yahoo-eng-team team mailing list archive

[Gabriel Samfira <samfiragabriel@xxxxxxxxx>]

Public bug reported:

For the most part cloud-init can initialize an instance inside oracle
compute using the EC2 metadata source provider.

There are however some aspects that do not work well, or at all. To
mention just a couple:

* initializing multiple NICs
* fetching metadata when the first NIC is a VNIC intead of a VEthernet nic
* Userdata can be a valid JSON. While a simple string is also a valid JSON, if the user decides a hashtable is more suitable, cloud-init should be able to look for a specific key


Here is some more info on the matter:

https://docs.oracle.com/cloud/latest/stcomputecs/STCSG/GUID-C391125C-
047A-4A77-BC96-8BF5E4BBE131.htm

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1675370

Title:
  Add Oracle compute metadata source provider

Status in cloud-init:
  New

Bug description:
  For the most part cloud-init can initialize an instance inside oracle
  compute using the EC2 metadata source provider.

  There are however some aspects that do not work well, or at all. To
  mention just a couple:

  * initializing multiple NICs
  * fetching metadata when the first NIC is a VNIC intead of a VEthernet nic
  * Userdata can be a valid JSON. While a simple string is also a valid JSON, if the user decides a hashtable is more suitable, cloud-init should be able to look for a specific key

  
  Here is some more info on the matter:

  https://docs.oracle.com/cloud/latest/stcomputecs/STCSG/GUID-C391125C-
  047A-4A77-BC96-8BF5E4BBE131.htm

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1675370/+subscriptions