- LINUXCN-23 Account for node.config location on LinuxCN
- TRITON-2349 Enable provisioning of instances past instance10
- TRITON-2304 New image server names
- TRITON-2266 cloudapi should be core
- TRITON-2228 Linux CN minimum viable product
- TRITON-2214 Z version bump in bind-obj-methods transient dependency broke several builds
- sdcadm#80 platform install --latest should not force linux on users
- TRITON-2194 provisionTmpVm should include metadata object
- TRITON-2148 Fix the '-s, --server' option for "sdcadm post-setup grafana".
- MANTA-5293 add GZ link to 'manta-hotpatch-rebalancer-agent' tool in the manta-deployment zone (when updating or deploying the 'manta' service).
- MANTA-4811 'sdcadm post-setup manta' now supports migrating from a mantav1 to a mantav2. See the following for full migration docs: https://github.com/TritonDataCenter/manta/blob/master/docs/operator-guide/mantav2-migration.md
- TRITON-2098 Fix a bug where
sdcadm platform
commands no longer worked.
- TRITON-2040 Fix a bug where
sdcadm post-setup manta
would not result in the created manta0 VM having an external NIC (required for it to function).
-
TRITON-2039 Fix a bug where
sdcadm up --all
would error out with:$ sdcadm up --all -y ... sdcadm up: error: no "manta" instance was found
if the DC has a "manta" SAPI service, but not instance of that service.
- TRITON-2016 sdcadm insts and sdcadm up fail if the dockerlogger image isn't in IMGAPI.
- TRITON-2009 EnsureMantaDeploymentGzLinksProcedure() breaks updating setups w/o manta instances
- MANTA-4817 sdcadm's detection of current mantav from $mantaApp.metadata.MANTAV is broken
-
TRITON-1979, TRITON-1981: Add
sdcadm post-setup manta
to be used to create the manta deployment zone. This will become the first step to deploying a Manta on Triton (https://joyent.github.io/manta/#deploying-manta) and will replace the old/usbkey/scripts/setup_manta_zone.sh
.By default this will create a manta deployment zone suitable for a "mantav2". See https://github.com/TritonDataCenter/manta/blob/master/docs/mantav2.md for details on mantav1 vs. mantav2.
- TRITON-1980 Add support for multiple valid image names for a service and update binder, mahi, moray, and prometheus to support both the "manta-" and "mantav2-" prefixed names in preparation of coming mantav2 images.
- TRITON-2001 Improve 'sdcadm up manta' to (re-)create the manta deployment symlinks in the GZ (e.g. /opt/smartdc/bin/manta-adm).
- TRITON-1991 Internal refactoring of finding an image when adding a service.
(This drops the undocumented support for specifying the string "default"
to the
-C, --channel
option ofsdcadm post-setup {grafana,logarchiver,kbmapi,firewall-logger-agent,prometheus}
.)
- TRITON-1907 output the correct command to install the docker service
- TRITON-1696 sdcadm should verify that triton_cns_enabled is set for the admin user before deploying prometheus
- TRITON-1744 Fix a crash in
sdcadm experimental remove-ca
if a given CNAPI server record does not have an "agents" field. - TRITON-1748 Ensure 'sdcadm experimental remove-ca' does trace logging to file.
- TRITON-1319 need firewall-logger agent (
sdcadm post-setup firewall-logger-agent
)
- TRITON-1730 Want
sdcadm post-setup common-external-nics
to not prompt for confirmation
- MANTA-3992 Add
sdcadm post-setup grafana
to setup a core Triton Grafana service. - TRITON-1656 Want new EnsureNicOnServiceInstances procedure in sdcadm
- TRITON-1700 update sdcadm to use 64 bit node (18.4)
- TRITON-1707
sdcadm post-setup prometheus
breaks if CNSallow_transfer
metadata does not exist yet
- TRITON-1706 'sdcadm post-setup dev-sample-data' will now ensure that sample images are public.
- TRITON-1670 sdcadm AddAllowTransferProcedure uses incorrect parameter name when listing service
- TRITON-1625 Have
sdcadm post-setup prometheus
add prometheus zone IP to CNS allow_transfer list - TRITON-1624 Change prometheus image name to "manta-prometheus" in sdcadm
- MANTA-3552 Add
sdcadm post-setup prometheus
to setup a core Triton Prometheus service.
- TRITON-1349 Subcommand
sdcadm post-setup kbmapi
using AddServiceProcedure
- TRITON-1298 Added
sdcadm post-setup logarchiver
, including new "AddServiceProcedure" procedure. - TRITON-1313 Random missing package failures running
sdcadm create
tests
- TRITON-1337
sdcadm experimental fix-core-vm-resolvers
broken
- TRITON-1307 Fix a few commands were broken in the TRITON-1300 change.
- TRITON-1305 Improvements to internal "Procedures" API. Convert 'sdcadm create'.
(Bad release. Upgrade to 1.24.10. See TRITON-1307.)
- TRITON-1300 Start improving CLI output with a
<cli>.ui
interface. So far onlysdcadm experimental update-gz-tools
has been updated to use it.
- TRITON-1293 Correct the interpretation of whether a server is running from
a CNAPI server object (CNAPI
<server>.transitional_status
is an implementation detail and not relevant for running status. This fixes a potential failure insdcadm post-setup docker
.
- TRITON-1276 sdcadm experimental update-gz-tools --latest --just-download dumps core
- TRITON-1272 sdcadm test failures due to outdated tape version
- TRITON-1236 steps.servers.selectServers for convenient -s/-S opt handling, add to 'sdcadm ex update-gz-tools'
- TRITON-954 sdcadm post-setup common-external-nics should be rack aware
- TRITON-1178 sdcadm man page build expects node in $PATH
- TRITON-754 lib/sdcadm.js is not admin rack aware
- TRITON-956 sdcadm procedures needs to be rack aware
- TRITON-948 sdcadm check-config shouldnt depend on admin NIC being tagged as "admin"
- TRITON-931 sdcadm admin IP functions need to be factored out
- TRITON-953 sdcadm checkCoreVmInstancesResolvers() needs to be rack aware
- TRITON-1004 sdcadm post-setup docker needs to be rack aware
- TRITON-1063 sdcadm experimental tests need update post TRITON-904
- TRITON-1055 sdcadm experimental update-agents with --just-download flag fails on SHA1
- TOOLS-2117 sdcnode updates for November 2018 node.js security releases
- TRITON-904 Needs some useful enhancements for "sdcadm experimental update-agents".
- TRITON-912 Agentshar update does not check for an ongoing agent update before running another agent installation.
- TRITON-889 Improvements to sdcadm's trace logging to file.
- TRITON-990 Change 'sdcadm check-health' and 'sdcadm check-config' to no longer write a trace log to file.
- TRITON-987 fabric setup broken by needless dependency on broken CA
- TOOLS-2114 sdcadm treats server as "unavailable" when it doesn't have a transitional_status
- TOOLS-2110 sdcadm can crash when SAPI instance has undefined image
- TRITON-722 "sdcadm health" still assumes each CN will have an "admin" nictag
- TRITON-723 Improve the output of unhealthy instances from
sdcadm health
.
- TRITON-619 Manatee upgrades broken due to SAPI not loading data from local storage and instead keep trying to download it from moray, with problems due to manatee being frozen during updates. This change modifies sdcadm behavior to freeze manatee shard only during manatee primary's update and also forces SAPI to load data from local storage by removing moray from DNS right after freezing the shard, bringing it back as soon as manatee's primary is operative again.
- TRITON-724 Fix a case where some sdcadm commands can exit with a
0
status when there is an error to report.
- TRITON-696 sdcadm want info subcommand, adds
sdcadm experimental info
- TRITON-689 improve
sdcadm post-setup cmon
to not require<server>.transitional_status
be defined on CNAPI server records.
- TRITON-313 walk back sdcadm steps export sugar
- TOOLS-1963
sdcadm create assets -s NEW-HEADNODE
should work - TOOLS-1962
sdcadm create sdc -s NEW-HEADNODE
should work - TOOLS-1966
sdcadm create -s dhcpd
should setdhcpd_server
flag to admin Nic - TRITON-636 trouble with timeouts in
sdcadm health
- TOOLS-1958 / TOOLS-1959
sdcadm experimental update-agents
Uses a consistent name for the downloaded agents shars and only retains a finite number.
- TRITON-574 sdcadm platform assign is broken with rack aware networking
- TRITON-572 sdcadm post-setup cloudapi should let sapi determine instance networks
- TOOLS-1896
sdcadm update sapi
could avoid using a temporary instance - TOOLS-1776
sdcadm health
can exit 0 when there are service errors - TRITON-477
sdcadm create $SVC --image
does not support channels - TOOLS-1926
sdcadm health
is stuck and won't exit - TRITON-417 sdcadm tests implicitly assume dev channel
- TOOLS-1699
sdcadm health -j
should always provide JSON even on exceptions - TOOLS-1569 sdcadm missing tests for ha-manatee
- TRITON-458 Remove JSStyle and Javascriptlint from sdcadm
- TRITON-347
sdcadm exp update-gz-tools --just-download
should not decompress and validate files - TRITON-395 Drop sdcadm support for manatee v1.0
- TRITON-455 sdcadm experimental doesn't load sdcApp when needed
- TOOLS-1717 sdcadm should not load SDC Application from SAPI when not required
- TOOLS-1345
sdcadm update manatee
does not update more than one async - TRITON-398 upgrade sdcadm to use node v6
- TRITON-325 sdcadm still aggressively gives up after updating non-HA moray
- TOOLS-1517
scdcam check-config
should not complain about missing docker/cns vars in SAPI
- TRITON-391 Get rid of sdcadm history
- TOOLS-1977 Modify
sdcadm post-setup ha-binder
to move insts to different servers - TOOLS-1224
sdcadm <subcommand> -h|--help
hits SAPI to get the sdc app: that's overkill
- TRITON-348 Support for using eslint
- TOOLS-1387
sdcadm platform install
should fail early if there's not enough free space on the USB. - TOOLS-2006
sdcadm platform usage
dumps core.
- TOOLS-1579
sdcadm post-setup ha-binder
should update core zones' resolvers. - Add
sdcadm experimental fix-core-vm-resolvers
as part of TOOLS-1579.
- Add
sdcadm post-setup volapi
to setup a core VOLAPI service. - Add
sdcadm experimental nfs-volumes
command to enable or disable various feature flags related to NFS volumes support for CloudAPI and sdc-docker.
- TOOLS-1899 Update to using node v4.
- TOOLS-1883 Allow 'sdcadm up manatee' to work correctly with newer MANATEE-346 changes which include multiple postgres versions.
- TOOLS-1842 Fix 'sdcadm create SERVICE-NAME -s SERVER' which was failing after TOOLS-1770 changes.
- TOOLS-1798 'sdcadm post-setup dev-sample-data' will now add a few sample packages for use with KVM instances.
- TOOLS-1767 Fix 'sdcadm up' to fail faster if there is a download error with on in a number of images.
- TOOLS-1634 'sdcadm up' parallel import of images can break when multiple images share a new origin image
- TOOLS-1728 sdcadm update for service with multiple instances should skip up-to-date ones
- TOOLS-1764 'sdcadm up SERVICE@VERSION' fails for services where the image name differs from the service name
- TOOLS-1731 'sdcadm post-setup common-external-nics' should set external network as primary
- TOOLS-1642: Use cueball HttpAgent to connect to Triton HTTP services.
- TOOLS-1704 'sdcadm post-setup cmon' requires CNS being setup
- TOOLS-1651 sdcadm create should support agent instances.
- TOOLS-1689 Fix a problem where
sdcadm
would hang on exit for many commands that used Ur.
- TOOLS-1683 'sdcadm experimental update AGENT' should support updates of individual instances.
- TOOLS-1685 make 'sdcadm ex' completion work.
- TOOLS-1681 sdcadm experimental update doesn't summarize properly when there are several agent updates.
- TOOLS-1644 'sdcadm create portolan' should be used for portolan HA setup.
- TOOLS-1648 sdcadm post-setup cmon should setup cmon-agent.
- TOOLS-1667 Deprecate 'sdcadm experimental cns' in favor of 'sdcadm post-setup cns'.
- Deprecate 'sdcadm experimental add-new-agent-svcs' and roll its functionality into 'sdcadm experimental update-other' and 'sdcadm experimental update-agent'. This allows the documented upgrade procedure to work unchanged, and not hit TOOLS-1665.
- TOOLS-1648 sdcadm post-setup cmon should setup cmon-agent
- TOOLS-1662: Fix 'sdcadm experimental add-new-agent-svcs' when adding new services.
- TOOLS-1574, TOOLS-1631: Fix
sdcadm experimental update AGENT
when there are no agent instances or missing service image uuids. - TOOLS-1633: Fix 'sdcadm up' of the assets zone. It was broken in version 1.15.0.
- TOOLS-1591: 'sdcadm up' of a number of core Triton services (the simple "stateless" ones, e.g. vmapi, napi, papi, etc.) will ensure the instance has a delegate dataset if required (if the SAPI service says it should have one).
- #28 Allow 'sdcadm create portolan --skip-ha-check' to work.
- TOOLS-1610 Drop the "-$buildstamp" suffix on the sdcadm image version field that was added by TOOLS-1599, because it breaks 'sdcadm self-update --latest'.
- TOOLS-1610 Bump ver as a workaround to get 'sdcadm self-update --latest' working.
- TOOLS-1499: add -C channel command line option to sdcadm experimental update-gz-tools.
- TOOLS-1429 sdcadm update-gz-tools /path/to/file does not work.
- TOOLS-1336 sdcadm should also update USB keys.
- TOOLS-1462: Modify update.md to reflect current update process reality.
- TOOLS-1434: Clearly explain SAPI update impediments and how to proceed.
- TOOLS-1272: Fix incorrect InternalError invocation.
- TOOLS-1414:
sdcadm self-update
reports channel in use. - TOOLS-1464/TOOLS-1467: Fix regression.
- TOOLS-1464/TOOLS-1467:
--ufds-backup-timeout
opt forsdcadm up
. - TOOLS-1425: Added
-C|--channel
option tosdcadm experimental update-agents
. - TOOLS-1464: Added
--ufds-backup-timeout
option tosdcadm up
(Set default to 10 mins). - TOOLS-1466:
sdcadm create
validates provided server before printing summary. - TOOLS-1465: When updating individual instances, check if those are part of HA setup.
- TOOLS-1272/TOOLS-1019: Use
sdc-usbkey
when avail. Do not mount/unmount usbkey when already mounted. - TOOLS-1405: Avoid errors emitted by ur client raise TypeError when trying to log/print them.
- TOOLS-1405: Prevent history raising "TypeError: Converting circular structure to JSON".
- TOOLS-1046: Make clear which API causes errors during
post-setup cloudapi
. - TOOLS-1384: Check for Ur availability when updating manatee instances not on the HN.
- TOOLS-1263/TOOLS-1046: Retry up to 5 times
platform assign|set-default
andpost-setup cloudapi
on connection or SDCClient errors. - TOOLS-1454:
sdcadm health
"quiet" and "json" options should not be mutually exclusive (Fixes GH-19). - TOOLS-1138/TOOLS-1263: Provided detailed information regarding APIs failing during booter caches update after platform assignment.
- TOOLS-1138/TOOLS-1263: Avoid false positive updating booter caches after platform assignment.
- TOOLS-1430: Added minimal validation of the presence of required files for update-gz-tools tarball.
- TOOLS-1439: removed hostvolumes from
update-docker
. Drop--servers
option. - TOOLS-1440: removed hostvolume service and hostvolume instances as part of
update-other
. - TOOLS-1441: removed nat setup from
update-docker
(Already intopost-setup fabrics
). - TOOLS-1438: replaced
sdcadm experimental update-docker
withsdcadm post-setup docker
andsdcadm update docker
. Emit deprecation warning when using the former update cmd. Setupdockerlogger
as part ofsdcadm post-setup docker
. - TOOLS-1381: Use dockerlogger instances created during dockerlogger setup.
Cleanup legacy CN UUIDs being used by dockerlogger instances before. Add
server, hostname and server_ip to dockerlogger instance list (same than for
other agents). Fixed typo which was preventing cabase and cainstsvc to be
updated through
sdcadm experimental update
. - TOOLS-1365:
sdcadm platform available
provides feedback when latest platform is already installed - TOOLS-1258: better error feedback for
common-external-nics
- TOOLS-1380: 'sdcadm insts' (and other code paths) crash on gather dockerlogger instance info
- TOOLS-1359:
sdcadm
no longer logs JSON-formatted bunyan logs tostderr
, preferring instead to emit actionable information formatted for human readability. The log data is still available in/var/log/sdcadm
. - TOOLS-1342:
sdcadm
now correctly respects longer execution timeouts for agent updates and docker deployments. - TOOLS-1367:
sdcadm
now connects more reliably to RabbitMQ when communicating with remoteur
agents. - TOOLS-1335:
sdcadm
will now retry DNS resolution for SAPI updates, avoiding one failure mode for any service updated immediately after abinder
update.
- TOOLS-1323: Split
sdcadm dc-maint
command into three subcommands due to incompatible options for each one of the tasks this command was trying to perform: start/stop and display DC maintenance status. - TOOLS-1326: Do not exit when there's an unknown service in SAPI, just warn about it.
- TOOLS-1301: sdcadm update cannot call method reprovFailLock_Lock of undefined
- TOOLS-1320: "sdcadm update dockerlogger" failed against multiple CNs
- TOOLS-1318: Added
--message
and--eta
options todc-maint --start
- TOOLS-1324: Added
--docker-only
and--cloudapi-only
options todc-maint --start
.
- TOOLS-1311: Updated to latest
cmdln
anddashdash
for better CLI completion.
- TOOLS-1298: Support for Underlay NICs provided by aggregations for
sdcadm post-setup underlay-nics
- TOOLS-1219:
sdcadm experimental update dockerlogger
will install/update dockerlogger service into setup servers. - TOOLS-1025: Use newest
manatee-adm
subcommands when possible.
- TOOLS-1293: Increase the timeout for the agents install step of
sdcadm experimental update-agents
to 20 minutes (from 10).
- TOOLS-1223: Set canmount=noauto for
zones/$ZONE_UUID/data/manatee
dataset when setting to something else. - TOOLS-1287: Renamed
sdcadm post-setup zookeeper
tosdcadm post-setup ha-binder
in order to make clear what type of VMs the command will create. - TOOLS-1121:
sdcadm update manatee
doesn't use the "sleep(60)" anymore and, instead, uses waitForInstToBeUp properly. - TOOLS-1289: Improved error messages when sysinfo-refresh fails for one or more servers during agents update.
- TOOLS-1076: Fixed help message for
post-setup zookeeper/binder
. - TOOLS-1191: Fixed PostgreSQL availability check.
- TOOLS-905: Move
dc-maint
out ofexperimental
. Now should be used just assdcadm dc-maint [options]
. - TOOLS-1187: Fixed
sdcadm update manatee
not properly freezing shard for updates.
- TOOLS-1277:
sdcadm experimental cns
to setup the CNS service and instance, andsdcadm up cns
to update. Note: Eventually this will move to either post-setup or being a default created service.
- TOOLS-1269: Always force
no_rabit=true
when updating agents
- TOOLS-1172: Reject
sdcadm up <unknown svc or inst>
with error msg - TOOLS-1239: Prevent
sdcadm up <svc>@<UUID of different svc image>
- TOOLS-1173: Fixed support for
sdcadm up <svc>@<version>
- TOOLS-1074: Added bash completion
- TOOLS-1264/TOOLS-563: Moved sdcadm subcommands to their own files and added
sdcadm experimental update
andscdadm experimental avail
which can handle individual updates (and availability) of vm, cn and net agents. - TOOLS-1252:
sdcadm avail sdcadm
andsdcadm avail
will now includesdcadm
available images without addingsdcadm
to SAPI services. (This may be modified in the future).
- TOOLS-1251:
sdcadm self-update
no longer updates to latest sdcadm available image and requires either a given image UUID or--latest
option to be provided.
- TOOLS-1246: sdcadm commands would break due to bad sshpk 1.5.0 release
- TOOLS-1225 Drop confusing
-x,--exclude SERVERS
options onsdcadm experimental update-agents ...
andsdcadm platform assign ...
. Also a number of robustness improvements tosdcadm experimental update-agents
.
- TOOLS-1167/TOOLS-1166: sdcadm ex update-agents now updates node.config in all CNs, has limited concurrency and agentsshar file download and execution are now two separated steps
- TOOLS-1236: 'sdcadm avail' doesn't need to print out channel info
- TOOLS-1234: 'sdcadm post-setup underlay-nics -h' for help doesn't work
- TOOLS-1031: 'sdcadm post-setup underlay-nics' verifies that CNs have the configured fabric underlay network tag assigned to any actual nic before trying to add them an otherwise useless underlay nic.
- Implemented changes from https://github.com/TritonDataCenter/rfd/tree/master/rfd/0009:
Replaced
sdcadm experimental fabrics
+sdcadm experimental portolan
withsdcadm post-setup fabrics
. Dropped support for--coal
option and added documentation about how to setup fabrics in CoaL to SDC's developers guide (https://github.com/TritonDataCenter/sdc/blob/master/docs/developer-guide/coal-post-setup-fabrics.md). - Get
sdcadm experimental default-fabric
out of experimental, i.e. now issdcadm default-fabric
.
- Deprecated 'latest' symlink for platforms
- Added
sdcadm platform set-default PLATFORM
subcommand - Include default platform column in
sdcadm platform list
- Added
sdcadm platform assign --latest
-
TOOLS-754: http_proxy support. If your SDC is firewalled of, but you have an HTTP proxy that can be used to given
sdcadm
(and IMGAPI) external access, then sdcadm can work with that.sapiadm update $(sdc-sapi /applications?name=sdc | json -H 0.uuid) \ metadata.http_proxy=http://my-proxy.example.com:8080
Then after a minute or two (to allow config-agents to update configurations appropriately) you should be able to 'sdcadm up ...' et al via that proxy.
A side-effect of this change is that programmatic usage of "lib/sdcadm.js" must explicitly finialize the
SdcAdm
instance:var SdcAdm = require('./lib/sdcadm'); var adm = new SdcAdm({...}); // ... adm.fini();
sdcadm experimental udpate-agents
now runs its own Ur Queue, instead of passing a script to each CN using sdc-oneachnode. Command options have been modified accordingly.
- Changed the behaviour of
sdcadm update --all --force-rabbitmq
andsdcadm update --all --force-data-path
to allow updating of rabbitmq and portolan (currently the sole "data path" service) along with the usual--all
services. - Allows
sdcadm avail
to show available updates for portolan and rabbitmq. - Added
sdcadm platform avail
- Added
--force-data-path
option for portolan upgrade
- Added
sdcadm avail(able)
. - Added
sdcadm channel get
- Added
-x|--exclude
option tosdcadm update
andsdcadm avail
. - Added
-k|--keep-latest
option tosdcadm platform remove
- Add support for installing custom TLS certificates for sdc-docker with
sdcadm experimental install-docker-cert
sdcadm experimental update-docker
now ensures that the zone has a delegate dataset
- Support full HA for
sdcadm update mahi
. - TOOLS-913, TOOLS-910, TOOLS-684 A number of fixes to properly support pulling and updating from channels other than the default.
- Add
sdcadm experimental default-fabric <UUID>
for adding a default fabric for a user
sdcadm experimental fabrics
now requires thesdc_nat_pool
property in its config for configuring the fabric NAT network pool.
- Added
--force
and--yes
option tosdcadm experimental update-agents
. - Added ability to continue from a previously failed run to
post-setup ha-manatee
.
- Added
sdcadm channel
to retrieve available update channels and set/unsetupdates_channel
into SAPI.
- Added
sdcadm experimental fabric
to initialize the SDC fabrics sub-system.
- Added
sdcadm platform
. Movedsdcadm experimental assign-platform
andsdcadm experimental install-platform
undersdcadm platform
command asassign
andinstall
. Also addedlist
,usage
andremove
subcommands.
- Modified
sdcadm post-setup zookeeper
to use binder images instead of zookeeper images. - Added
sdcadm rollback
- Added DNS to docker and portolan instances.
- Stop lying regarding image used for ha-manatee.
- Added
--just-download
option tosdcadm experimental update-gz-tools
andsdcadm experimental update-agents
.
- Added
sdcadm experimental portolan
to add/update the portolan service. - Everything
sdcadm experimental
added tosdcadm history
.
- Added
sdcadm create <service> --server=<UUID> [--image=<UUID>]
. - Moved
sdcadm experimental add-2nd-manatee
tosdcadm post-setup ha-manatee
and include creation of 3rd manatee instance as part of it.
- Add
sdcadm post-setup zookeeper
to create the zookeeper service and add a cluster of zookeeper instances. - Added
sdcadm update zookeeper
. - Added a warning for users when an image download fails due to the lack of external nic for IMGAPI
- Save
self-update
changes into history. - Save history into SAPI when available.
- Add
sdcadm experimental update-docker
to add/update the docker service && docker0 instance. - Added post-setup commands,
cloudapi
,common-external-nics
- Add
sdcadm experimental install-platform
andsdcadm experimental assign-platform
- Add
sdcadm check-health
as an eventual replacement forsdc-healthcheck
.
- Add
sdcadm experimental add-new-agent-svcs
. - Support full HA for
sdcadm update moray
.
- Add
sdcadm update mahi
with support for creating a delegate dataset - Add
sdcadm update binder
- Add
sdcadm experimental update-gz-tools
to be able to update global zone tools - Add
sdcadm update manatee
both, for HA setups and single dev VM. - Add
sdcadm experimental add-2nd-manatee --server=<UUID>
to create the second manatee VM for HA.
- Add
sdcadm experimental update-agents
to be able to update agents
- Add --all flag for updating all available services at once.
- Add
sdcadm update sapi
, limited to a single instance on the headnode. - Add
sdcadm update moray
, limited to a single instance on the headnode. - Add
sdcadm update ufds
, limited to a single instance on the headnode.
-
Add
sdcadm update --force-same-image ...
to be able to for an update/reprovision of an instance using the same image. Usually that would be a no-op. -
sdcadm update
can now update imgapi, limited to a single imgapi instance on the headnode. -
Add
sdcadm experimental update-other
temporary grabbag of SDC update steps.
- Add
sdcadm experimental dc-maint
for starting and stopping DC maintenance mode (i.e. putting cloudapi in readonly mode).
- Add --force-rabbitmq flag and prevent updating of RabbitMQ if flag not used.
-
TOOLS-582 correct bug in self-update that would break when multiple build branches were available.
-
TOOLS-581 a self-update that finds no updates should not create a /var/sdcadm/self-updates dir
-
Add 'sdcadm check-config'.
-
Add 'sdcadm experimental ...' where experimental commands will hang until fully integrated into the planned upgrade process.
- Save old user-script to 'sdcadm update' work dir for possible rollback.
config.vmMinPlatform
guard for minimum platform supported for core VM updates.sdcadm svcs
lists one service per row, JSON is mostly from SAPI's ListServices.sdcadm insts -I
to group by (service, image) unique pairs
- 'sdcadm update' will correctly do nothing (saying "Up-to-date") if the given services are already at the latest candidate image. It also now properly excludes images published earlier than the currently used image as update candidates.
- 'sdcadm update @' and other calling forms
- Change shar self-installer input envvar from SDCADM_LOGDIR to SDCADM_WRKDIR.
- 'sdcadm update -I ...'
- First stab at
sdcadm update SERVICE
. Currently limited to most of the stateless services (e.g. vmapi, cnapi) with just a single instance, and only on the headnode.
- TOOLS-437:
sdcadm instances
,sdcadm services
.
- TOOLS-436:
sdcadm self-update
First version.