Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update of goconserver is not tracked with xCAT-core/dep changes #36

Open
whowutwut opened this issue Apr 4, 2018 · 2 comments
Open

Comments

@whowutwut
Copy link
Member

Looks like there's no automatic update of goconserver per our instructions for updating xCAT product.

Currently we document, to update xCAT (using yum):

yum update "*xCAT*" "*xcat*" 

This will not pull in any goconserver updates...

How do we feel we should handle this?

@whowutwut
Copy link
Member Author

I was able to update using: yum update "*xCAT*" "*xcat*" "goconserver*"

@chenglch
Copy link
Contributor

chenglch commented Apr 9, 2018

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants