Skip to content

Releases: Teradata/stacki

5.1rc5a

12 Sep 22:44
Compare
Choose a tag to compare

Feature

  • dump and load in yaml or json

  • stack dump refactor

    Move code from pluggins into commands:

    • stack dump api
    • stack dump appliance
    • stack dump bootaction
    • stack dump box
    • stack dump cart
    • stack dump environment
    • stack dump group
    • stack dump host
    • stack dump network
    • stack dump os
    • stack dump pallet

05.02.06.05

12 Sep 20:31
Compare
Choose a tag to compare
stacki-05.02.06.05

INTERNAL: Rev version for release `05.02.06.03`

05.02.06.04

12 Sep 20:32
3f27c66
Compare
Choose a tag to compare

Feature

  • Added support for target,*,1,*, in storage CSV.

    This will pair up drives and put them in a RAID 1 configurations.

  • setting Kickstart_PrivateDNSServers to ' ' removes nameserver line from /etc/resolv.conf

    Also if no Public and Private DNSServers are defined don't setup stacki DNS to forward.

Bugfix

  • Cleanup how hostnames for "run" commands are calculated

  • Tell logrotate it's ok to skip rotating missing logs instead of erroring. Also include local0 in rotation, and make the log rotatio
    n size 100M for all logs in stack.conf

    The logrotate file is laid down via SUX, so existing frontends can get an approximation of this fix with:

    sed -i 's/local\[1/local\[0/' /etc/logrotate.d/stack
    sed -i '1s;^;size=100M\nmissingok\n;' /etc/logrotate.d/stack
    logrotate /etc/logrotate.conf -d 2>/dev/null && echo "success"
    

Git

  • Merge branch 'support/05.02.06.x' of github.com:/Teradata/stacki into support/05.02.06.x

  • Fix test to match new code.

05.02.06.03

12 Sep 20:32
Compare
Choose a tag to compare

Bugfix

  • Fix NTP code for frontends.

5.3

08 Mar 22:33
Compare
Choose a tag to compare
5.3

Feature

  • Update foundation-python to python-3.7.2

    This also updates the sles11.3 installation environment's python and foundation-python-packages.

Git

  • start 05.03.00.00

  • Merge branch 'master' into develop

05.02.06.01

08 Mar 22:32
Compare
Choose a tag to compare

Bugfix

  • Keep health message out of the YaST 2nd stage

  • comments in rsyslog broke for SLES11

Git

  • Merge branch 'release/05.02.06.01'

  • starting 05.02.06.01

  • Merge branch 'release/05.02.06.00' into develop

  • Merge branch 'release/05.02.06.00'

05.02.06.00

08 Mar 22:31
Compare
Choose a tag to compare

Feature

  • Add cluster-up tool to tools directory

  • Move the frontend to its own box

    Doing this so run pallet becomes simpler and doesn't change
    the box used for backend nodes. default box is remains for that.

Bugfix

  • We have more than a default box now, update test accordingly

  • Find and check all RPMS regardless of architecture

  • Treat certain scenarios in manifest-check and get3rdparty as errors

    This updates manifest-check.py to return a nonzero exit code if there
    are no manifest files found.

    This also updates get3rdparty.py to return a nonzero exit code if it
    fails to fetch a 3rd party package.

  • Make enable pallet error message more explicit

    When a pallet is trying to be enabled after being added, if a parameter mismatches,
    the stack command would just say the pallet isn't valid. This isn't a clear enough
    error message to the user so instead the error message was made more explicit. Now
    when the same thing occurs, the error message includes a list of the parameters entered.

  • dump of carts matches pallets

  • really send ws logs to /var/log/local1

05.02.05.00

08 Mar 22:31
Compare
Choose a tag to compare

Bugfix

  • Add check for malformed gateway addresses in Installer

  • Fix add pallet when /mnt/cdrom unavailable

  • add 'remove pallet' to the list of sudo'd web service commands

  • make 'create new pallet' default to creating a pallet that matches the current OS, not 'sles'

  • Use correct variable

    Incorrect variable referenced

  • Add leading zeros to ID of script section

    When post sections are generated, boot-post sections are generated
    according to Stacki ordering, but are run in a lexical order. This
    means that boot-post-20 is run after boot-post-100. If there was
    an explicit ordering specified in Stacki, this ordering can get
    ignored when AutoYaST actually runs.

    Fix this by making the script ID a 4-digit ID with leading zeros.
    'Cuz we'll never have more than 9999 sections in a node file. /flw

  • Fix Intrinsic firewall for frontend

    iptables rule had a syntax error. Fix

  • for previous bugfix

  • Autogeneration of release notes broke for some tags

Git

  • starting 05.02.05.00

  • Merge branch 'release/05.02.04.00' into develop

  • Merge branch 'release/05.02.04.00'

05.02.04.00

13 Feb 20:23
Compare
Choose a tag to compare

Feature

  • Add ability to override reported files

    Only for /etc/resolv.conf right now. Added reportFile method
    for generating tags.

    If an attribute etc_resolv.conf is defined the value will be used
    rather than the generated report.

  • Run test-framework integration tests in parallel

    The tests are distributed across 4 cpus inside of the VM. Minor special handling for database
    names needed to be added to the stack command code to point everything at a copy of the database
    the test-framework manages. Each test file is pinned on the same process and it's test function
    s ran sequentially, which seems to keep things happy.

    A new fixture named exclusive_lock has been added to allow your test to run with exclusive c
    ontrol of the VM. It does this by waiting for the other test processes to finish their tests, th
    en pause them before they can start the next one. Only a few tests and fixtures that use shared
    resources (modify the filesystem, start servers on ports, inject code, etc) have needed this ext
    reme step. Only use it if your test won't pass without it.

    A second new fixture, named debug_log, has also been added. You add it to your other fixture
    s or tests and then call as a function. You give it a string and it will write it to a debug.lo\ g file in the reports directory, along with the test making the call and the xdist worker it is
    running on. Useful for debugging pytest fixtures because pytesst swallows normal print calls. Y
    ou should remove any debug_log calls from your code before merging into develop, because wri
    ting to the shared log isn't very efficient.

    I added a new --audit flag to the run-tests.sh script for the integration test suite. This
    will log any modifications to the /etc, /export/stack/pallets, and /export/stack/carts di
    rectories, and warn you at the end of testing if any of the tests are missing the fixtures to re
    very the filesystem modifications.

Bugfix

  • WS message to /var/log/local1

Git

  • start 05.02.04.00

  • Merge branch 'release/05.02.03.00' into develop

05.02.03.00

13 Feb 20:22
Compare
Choose a tag to compare

Feature

  • Add a parameter to 'list host attr' to separate the display of common and distinct attributes.

    'stack list host attr display=[all|common|distinct] [hosts...] [attr=]' changes which at
    tributes are displayed.

    display=all will display all attributes for each host, grouped by host. This is the default,
    traditional behavior.

    display=common will display only attributes which are identical for each host, under the name
    'common'.

    display=distinct will display only attributes which are not identical for each host.

Bugfix

  • Prevent infinite recusion when there is no search line in resolv.conf

  • Force the CSV files to be ascii during CSV based load commands

Git

  • start 05.02.03.00

  • Merge branch 'release/05.02.02.00' into develop