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.

Sign up for GitHub

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

Jump to bottom

Pull nightly photon builds #27

Closed
hickeng opened this issue Jan 26, 2016 · 0 comments
Closed

Pull nightly photon builds #27

hickeng opened this issue Jan 26, 2016 · 0 comments
Assignees
@caglar10ur
Labels
area/appliance area/kernel

Comments

@hickeng
Copy link
Member

hickeng commented Jan 26, 2016

In order to see and address breakages early, we want to move to using photon nightly builds as our base. This has a dependency on #16
cristianfalcone pushed a commit to cristianfalcone/vic that referenced this issue Aug 9, 2017
@jooskim
Show datastores only belonging to the selected compute resource (vmwa…
c0bcb52 
…re#27)

* [WIP] Use datastores only attached to cluster

* Fix typo

* Show only datastores linked to the chosen cluster

* Remove unnecessary imports from wizard module

Also update the logic for updating the datastores select input
as the user changes the compute resource in the Compute Capacity
section.

* Set endpoint VM memory max value up to maxUsage

This commit prevents the next button from getting disabled
automatically in the Compute Capacity section when the user selects
a host or cluster that has less than 2048MB of ram available for
VM endpoint. As a solution, we set the smaller value between 2048
and memory['maxUsage'] so that the validation doesn't disable the
next button after selecting a host/cluster.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caglar10ur caglar10ur

Labels
area/appliance area/kernel
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dougm @caglar10ur @hickeng