You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@whowutwut , as you said, user has to upgrade goconserver manually.
The habit of xcat to setup or upgrade dependency packages rely on the RPM or DEB heavily, but this is not flexible enough especially when installing or upgrading a xcat cluster.
My opinion is that some work of xcat should be move to the orchestration tool like ansible or others. For example, if we ship a playbook to setup or upgrade xcat, user could simply specify something like below to decide which one to setup.
dependencies:
console: goconserver, confluent or conserver
openbmc: perl or python
xcat-inventory: true
The steps about CA , certificate generation could also be moved to the playbook.
Looks like there's no automatic update of
goconserver
per our instructions for updating xCAT product.Currently we document, to update xCAT (using
yum
):This will not pull in any goconserver updates...
How do we feel we should handle this?
The text was updated successfully, but these errors were encountered: