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

[RI2 Ch4] Placeholder: Airship-based RI2 included in chapter04.md. #2041

Open
tomkivlin opened this issue Sep 30, 2020 · 5 comments
Open

[RI2 Ch4] Placeholder: Airship-based RI2 included in chapter04.md. #2041

tomkivlin opened this issue Sep 30, 2020 · 5 comments
Assignees
Labels
Projects

Comments

@tomkivlin
Copy link
Collaborator

To be replaced by more specific issues as needed.

@tomkivlin tomkivlin created this issue from a note in RI2 (To do) Sep 30, 2020
@tomkivlin
Copy link
Collaborator Author

@pgoyal01 could you work with James to spawn some more useful and specific issues for this please?

@jgu17 jgu17 assigned jgu17 and unassigned pgoyal01 Sep 30, 2020
@tomkivlin
Copy link
Collaborator Author

@pgoyal01 @jgu17 - are there any updates on this please? Just wondering if we need to work out any dependencies that need issues raising?

@jgu17
Copy link
Collaborator

jgu17 commented Nov 4, 2020

@tomkivlin yes, there are a couple of dependencies: acquire a pod in LAAS for CNTT Airship 2.0 installer (WIP); Airship 2.0 release (expect in 1Q 2021).

I checked out the current chapter. It looks good but needs to be organized to allow to add the content for a second RI installer besides kuberef. That could be the first task once we are getting close to AS 2.0 availability?

@tomkivlin
Copy link
Collaborator Author

AS 2.0 available last week. @jgu17 are you able to do a brief PR for this in the next week please? If not, we can move to backlog.

@jgu17
Copy link
Collaborator

jgu17 commented Jan 6, 2021

@tomkivlin It was only the AS 2.0 beta. The production release is sometime in Q1 2021 (we may have a better idea of the exact date next week). We've identified the POD to use for AS 2.0 which should be ready for us by the end of this week or next week. We will put AS 2.0 production release (when it is released) on the new POD and create content for this chapter based the AS 2.0 deployment in the CNTT lab. The new POD is HPE server, so there will be some new development work expected to support the HPE hardware. Long story short, we won't make it next week.

@tomkivlin tomkivlin added Backlog and removed Elbrus labels Jan 6, 2021
@project-bot project-bot bot moved this from To do to Backlog in RI2 Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
RI2
  
Backlog
Development

No branches or pull requests

3 participants