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

Support inventory folders when creating new resources #3619

Closed
dougm opened this issue Jan 17, 2017 · 9 comments
Closed

Support inventory folders when creating new resources #3619

dougm opened this issue Jan 17, 2017 · 9 comments
Labels
area/vmc Epic Represents a ZenHub Epic kind/feature New functionality you could include in marketing material priority/p1 source/customer Reported by a customer, directly or via an intermediary team/foundation

Comments

@dougm
Copy link
Member

dougm commented Jan 17, 2017

As a customer, I want to use vCenter inventory folders to organize inventory resources created by VIC so that I can apply management operations at the inventory folder level, such as RBAC.

Both vic-machine and VCH should support creating resources within inventory folders for existing types:

  • VirtualApp

  • VirtualMachine

And consider type we may create in the future, such as:

  • DistributedVirtualPortgroup

At a minimum, we should support the use of existing inventory folders, but could also support creating inventory folders as a convenience.
@dougm dougm added priority/p2 kind/feature New functionality you could include in marketing material labels Jan 17, 2017
@dougm dougm mentioned this issue Jan 31, 2017
Closed
@emlin emlin mentioned this issue Feb 1, 2017
Closed
@emlin emlin added the source/customer Reported by a customer, directly or via an intermediary label Feb 2, 2017
@stuclem stuclem mentioned this issue Feb 7, 2017
Closed
@dougm dougm mentioned this issue Feb 14, 2017
Closed
@mdubya66 mdubya66 added the impact/doc/note Requires creation of or changes to an official release note label Mar 6, 2017
@stuclem
Copy link
Contributor

stuclem commented Mar 7, 2017

Proposed text for 0.9 release notes:

  • vic-machine and VCH do not support creation of resources within inventory folders. #3619
    This capability will be added in a future release.

@dougm does this cover it?

@dougm
Copy link
Member Author

dougm commented Mar 7, 2017

@stuclem 👍

@stuclem
Copy link
Contributor

stuclem commented Mar 7, 2017

Thanks @dougm. Removing kind/note.

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label Mar 7, 2017
@stuclem stuclem mentioned this issue Mar 22, 2017
Open
@mdubya66 mdubya66 mentioned this issue Mar 25, 2017
Closed
@mdubya66 mdubya66 added this to the Sprint 12 milestone Jun 20, 2017
@mhagen-vmware mhagen-vmware modified the milestones: Sprint 13, Sprint 12 Jul 18, 2017
@mdubya66 mdubya66 removed this from the Sprint 13 milestone Aug 1, 2017
hickeng pushed a commit that referenced this issue Nov 16, 2017
@mhagen-vmware @hickeng
Update tests to support resource pool based VCH (#6772)
4e3a005 
Moving to resource pools requires that we alter the way in which a govc search filter is specified.
The current form of `vch-name/vch-name` requires the VCH be deployed into an inventory
folder which is not the case without #3619
AngieCris pushed a commit to AngieCris/vic that referenced this issue Nov 20, 2017
@mhagen-vmware @AngieCris
Update tests to support resource pool based VCH (vmware#6772)
b61aec9 
Moving to resource pools requires that we alter the way in which a govc search filter is specified.
The current form of `vch-name/vch-name` requires the VCH be deployed into an inventory
folder which is not the case without vmware#3619
@matthewavery matthewavery added the Epic Represents a ZenHub Epic label Jan 4, 2018
@matthewavery
Copy link
Contributor

Converting this to an epic. There are three things that need to be done for this issue. Issues are being made for these and added now. @pdaigle

@matthewavery
Copy link
Contributor

There appears to be a dependency chain here as well. Looks like #7032 must be done first, then #7025. Then #4326. This is due to the fact that the VCH is not created under it's own folder. noted from PR #6772 commit named Update tests to support resource pool based VCH

@zjs
Copy link
Member

zjs commented Jan 5, 2018

It seems like this and #773 are both epics, but it's not clear to me what's tracked by one vs. the other.

@hickeng
Copy link
Member

hickeng commented Feb 5, 2018

Adding to 1.4 as this will be an organisational issue for large numbers of containerVMs at scale, and also impacts the granularity with which we can apply security permissions.

@hickeng
Copy link
Member

hickeng commented Feb 13, 2018

left #4326 as a child of only #773 - it is likely to be fixed by this work, but isn't technically part of it. It's a bug in existing support, not part of new function.

@mdubya66
Copy link
Contributor

All issues completed. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/vmc Epic Represents a ZenHub Epic kind/feature New functionality you could include in marketing material priority/p1 source/customer Reported by a customer, directly or via an intermediary team/foundation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@dougm @zjs @cgtexmex @emlin @hickeng @matthewavery @mdubya66 @stuclem @mhagen-vmware