Skip to content
This repository was archived by the owner on Jul 24, 2019. It is now read-only.

Conversation

@larryrensing
Copy link
Contributor

What is the purpose of this pull request?:
This gives users an option to load nova with a basic flavor.

What issue does this pull request address?: partial fix for #201

Notes for reviewers to consider:
The setting of env vars in bootstrap.sh will change when #273 is merged

Specific reviewers for pull request:
@intlabs @alanmeadows

Copy link
Contributor

@intlabs intlabs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good so far @larryrensing :) just a few comments.

nova/values.yaml Outdated
service:
- mariadb
bootstrap:
jobs:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the bootstrap job need to be dependent on any jobs itself? I think these can most likely all be safely removed, as it is only really dependent on the nova & keystone api's.

nova/values.yaml Outdated
- keystone-db-init
- mariadb-seed
service:
- mariadb
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be safe to remove this dependency - as the bootstrap job will only be dependent on the api's themselves, and not the db backing them.

nova/values.yaml Outdated
enabled: true
flavors:
m1:
tiny:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it would probably be better to have this as a single key, eg m1_tiny rather than a nest.

Copy link
Collaborator

@v1k0d3n v1k0d3n Mar 16, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 would like see this as well. and this should really be something where company "acme" could add a list of flavors, no? even personally, i always have my 20 or so flavors after every fresh installation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed


wait_for_api

nova flavor-show {{ .Values.bootstrap.flavors.m1.tiny.name }} || \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it be possible to expand this to an arbitrary number of flavors, specified in the values.yaml?

TIMEOUT=120
#larryrensing: sleep to wait until nova api is actually serving on
# the appropriate port. not pretty, there has to be a cleaner approach to this
sleep 30
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving to direct service checking along the lines of: #143 would remove this limitation of kubernetes-entrypoint to determine if a service is ready to receive requests. Until then is the sleep and the while statement needed or could we reduce it to one? If the job initially fails it presumably restarts wich may be a simpler, yet less pretty, way to deal with this.

@v1k0d3n v1k0d3n self-requested a review March 16, 2017 21:31
nova/values.yaml Outdated
enabled: true
flavors:
m1:
tiny:
Copy link
Collaborator

@v1k0d3n v1k0d3n Mar 16, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 would like see this as well. and this should really be something where company "acme" could add a list of flavors, no? even personally, i always have my 20 or so flavors after every fresh installation.

function wait_for_api {
TIMEOUT=120
#larryrensing: sleep to wait until nova api is actually serving on
# the appropriate port. not pretty, there has to be a cleaner approach to this
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

were you planning on removing this statement, or just your github handle? i'd really like to remove the personal references (notes are fine). trying to catch them when we see them.

@larryrensing larryrensing force-pushed the feat/bootstrap-services-nova branch from 54e8c03 to 3cd21f9 Compare March 16, 2017 22:35
- name: nova-bin
configMap:
name: nova-bin
{{- end -}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #294 for comments on whether the job is conditional or the work is conditional.

export HOME=/tmp


function wait_for_api {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why aren't we guaranteed this with the dependency checks? If we're not, we may want to investigate there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As @intlabs said on #294, the newest version of entrypoint may address the service dependency weirdness.

}

cat <<EOF>/tmp/openrc
export OS_USERNAME={{.Values.keystone.admin_user}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't there a helm-toolkit macro for this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - it was merged after this PR was submitted, a rebase is needed

@larryrensing larryrensing force-pushed the feat/bootstrap-services-nova branch from 79ae872 to 3d82041 Compare March 20, 2017 16:58
@v1k0d3n v1k0d3n added this to the 0.3.0 milestone Mar 22, 2017
Copy link
Contributor

@alanmeadows alanmeadows left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good Larry. We can continue to enhance this.

@alanmeadows alanmeadows merged commit afcf1c9 into att-comdev:master Apr 1, 2017
@v1k0d3n v1k0d3n removed the ready label Apr 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants