Feature #11802
Ability to add custom information to the EC2 USER META DATA
100%
CMS
Description
CMS would like to add custom information to user meta data in case of CERN Micro VM. This information is required and will be useful to customize the VM before glidein startup extracts the metadata. Information can be passed on to the VM through factory configuration. Ideally extremely slimmed down version of pilot-launcher can do this by using pilot's python libraries. However, because of the way CERN micro VMs are setup/deployed/launched, python is not available in the system.
NOTE:
- We may need to add a new configuration tag that is looked at in case of VMs and when we generate the userdata.ini file with this content
- Glideinwms compresses and encodes the metadata, so even if we support custom info, VO needs to perform similar task that pilot launcher does.
Subtasks
History
#1 Updated by Parag Mhashilkar over 4 years ago
- Assignee set to Parag Mhashilkar
- Target version set to v3_2_x
#2 Updated by Dirk Hufnagel over 4 years ago
We want to use this mechanism to pass information in the EC2 user data that is then used to customize the VM itself. As such, the information in question is outside the scope of gWMS and preferably should not be compressed or encoded by gWMS. If for code design reasons this isn't easy to do, we could most likely also live with an encoding scheme that is relatively easy to undo without any gWMS code tools.
#3 Updated by Dirk Hufnagel over 4 years ago
What we would prefer is if we could add (uncompressed)
[ucernvm begin]
cvmsf_proxy=...
[ucernvm end]
directly to the ec2 user data.
#4 Updated by Marco Mambelli about 2 years ago
- Target version changed from v3_2_x to v3_4_x
#5 Updated by Marco Mambelli almost 2 years ago
- Target version changed from v3_4_x to v3_5_x
#6 Updated by Marco Mambelli 9 months ago
- Target version changed from v3_5_x to v3_6_x