why associating tags to vms taking too long time by using VMware-vCloud-Suite-SDK-Python-6.0.0?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Hi all:
Our team needs to create tags in our Vcenter(about 2000 virtualmachines in our vcenter) by VMware-vCloud-Suite-SDK-Python-6.0.0. And the first two steps(create tag and create category) had gone well, but when we do the third step(association tag by name or ip), it was consuming too much time in this step(about 40-60 s for one host),in our environment every host has nine tags, so we must associate nine times for every host.
I would like to know if this is nomal? And if it’s not, could you please give me a solution or reference ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the tag-association step with VMware-vCloud-Suite-SDK-Python-6.0.0 against a comparable vCenter, measuring one association and the repeated nine-per-host workflow. Review the SDK calls used for tag and category creation and association. Done means establishing whether the timing is expected and documenting a confirmed cause, workaround, or reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100