os_mapping.rst 6.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. OpenStack - Labeled Resources
  2. -----------------------
  3. +------------------------+------------------------+-----------+----------------+----------+
  4. | Labeled Resource | OS Resource Type | CB ID | CB Name | CB Label |
  5. +------------------------+------------------------+-----------+----------------+----------+
  6. | OpenStackInstance | Instance | ID | ID | Name |
  7. +------------------------+------------------------+-----------+----------------+----------+
  8. | OpenStackMachineImage | Image | ID | ID | Name |
  9. +------------------------+------------------------+-----------+----------------+----------+
  10. | OpenStackNetwork | Network | ID | ID | Name |
  11. +------------------------+------------------------+-----------+----------------+----------+
  12. | OpenStackSubnet | Subnet | ID | ID | Name |
  13. +------------------------+------------------------+-----------+----------------+----------+
  14. | OpenStackRouter | Router | ID | ID | Name |
  15. +------------------------+------------------------+-----------+----------------+----------+
  16. | OpenStackVolume | Volume | ID | ID | Name |
  17. +------------------------+------------------------+-----------+----------------+----------+
  18. | OpenStackSnapshot | Snapshot | ID | ID | Name |
  19. +------------------------+------------------------+-----------+----------------+----------+
  20. | OpenStackVMFirewall | Security Group | ID | ID | Name |
  21. +------------------------+------------------------+-----------+----------------+----------+
  22. The resources listed above are labeled, they thus have both the `name` and
  23. `label` properties in CloudBridge. These resources require a mandatory `label`
  24. parameter at creation. For all labeled resources, the `label` property in OpenStack
  25. maps to the Name attribute. However, unlike in Azure or AWS, no resource has
  26. an unchangeable name by which to identify it in our OpenStack implementation.
  27. The `name` property will therefore map to the ID, preserving its role as an unchangeable
  28. identifier even though not easily readable in this context. Finally, labeled resources
  29. support a `label` parameter for the `find` method in their corresponding services.
  30. The below screenshots will help map these properties to OpenStack objects in the
  31. web portal.
  32. .. figure:: captures/os-instance-dash.png
  33. :scale: 50 %
  34. :alt: name, ID, and label properties for OS Instances
  35. The CloudBridge `name` and `ID` properties map to the unchangeable
  36. resource ID in OpenStack as resources do not allow for an unchangeable
  37. name. The `label` property maps to the 'Name' for all resources in
  38. OpenStack. By default, this label will appear in the first column.
  39. OpenStack - Unlabeled Resources
  40. ---------------------------
  41. +-----------------------+------------------------+-------+---------+----------+
  42. | Unlabeled Resource | OS Resource Type | CB ID | CB Name | CB Label |
  43. +-----------------------+------------------------+-------+---------+----------+
  44. | OpenStackKeyPair | Key Pair | Name | Name | - |
  45. +-----------------------+------------------------+-------+---------+----------+
  46. | OpenStackBucket | Object Store Container | Name | Name | - |
  47. +-----------------------+------------------------+-------+---------+----------+
  48. | OpenStackBucketObject | Object | Name | Name | - |
  49. +-----------------------+------------------------+-------+---------+----------+
  50. The resources listed above are unlabeled. They thus only have the `name`
  51. property in CloudBridge. These resources require a mandatory `name`
  52. parameter at creation, which will directly map to the unchangeable `name`
  53. property. Additionally, for these resources, the `ID` property also maps to
  54. the `name` in OpenStack, as these resources don't have an `ID` in the
  55. traditional sense and can be identified by name. Finally, unlabeled resources
  56. support a `name` parameter for the `find` method in their corresponding
  57. services.
  58. .. figure:: captures/os-kp-dash.png
  59. :scale: 50 %
  60. :alt: KeyPair details on OS dashboard
  61. KeyPairs and other unlabeled resources in OpenStack have `name` that is
  62. unique and unmodifiable. The `ID` will thus map to the `name` property when
  63. no other `ID` exists for that OpenStack resource.
  64. OpenStack - Special Unlabeled Resources
  65. -----------------------------------
  66. +--------------------------+------------------------+-------+------------------------------------------------------------------------+----------+
  67. | Unlabeled Resource | OS Resource Type | CB ID | CB Name | CB Label |
  68. +--------------------------+------------------------+-------+------------------------------------------------------------------------+----------+
  69. | OpenStackFloatingIP | Floating IP | ID | [public_ip] | - |
  70. +--------------------------+------------------------+-------+------------------------------------------------------------------------+----------+
  71. | OpenStackInternetGateway | Network `public` | ID | 'public' | - |
  72. +--------------------------+------------------------+-------+------------------------------------------------------------------------+----------+
  73. | OpenStackVMFirewallRule | Security Group Rule | ID | Generated: [direction]-[protocol]-[from_port]-[to_port]-[cidr]-[fw_id] | - |
  74. +--------------------------+------------------------+-------+------------------------------------------------------------------------+----------+
  75. While these resources are similarly unlabeled, they do not follow the same
  76. general rules as the ones listed before. Firstly, they differ by the fact
  77. that they take neither a `name` nor a `label` parameter at creation.
  78. Moreover, each of them has other special properties.
  79. The FloatingIP resource has a traditional resource ID, but instead of a
  80. traditional name, its `name` property maps to its Public IP.
  81. Moreover, the corresponding `find` method for Floating IPs can thus help
  82. find a resource by `Public IP Address`.
  83. In terms of the gateway in OpenStack, it maps to the network named 'public.'
  84. Thus, the internet gateway create method does not take a name parameter, and
  85. the `name` property will be 'public'.
  86. Finally, Firewall Rules in OpenStack differ from traditional unlabeled resources
  87. by the fact that they do not take a `name` parameter at creation, and the
  88. `name` property is automatically generated from the rule's properties, as
  89. shown above. These rules can be found within each Firewall (i.e. Security
  90. Group) in the web portal, and will not have any name in the OpenStack dashboard.