Integration with HP Cloud

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Unknown Unknown
  • Resolution: Fixed
  • Affects Version/s: 0.6.10
  • Fix Version/s: None
  • Component/s: cloud
  • Labels:
  • Environment:

    HP Cloud Services ( http://www.hpcloud.com/ )

Description

The current plugins for Cloud (ec2/euca/openstack etc.) do not pick up the meta-data from HP Cloud.

The fix is a simple one and has already been tested on my own VMs.

See pull request: https://github.com/opscode/ohai/pull/59

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matt Ray added a comment -

This is a good start, it works on my HP nodes and I'll make sure it's feature-compatible with ec2 and rackspace nodes as I flesh out knife-hp (https://github.com/mattray/knife-hp)

Show
Matt Ray added a comment - This is a good start, it works on my HP nodes and I'll make sure it's feature-compatible with ec2 and rackspace nodes as I flesh out knife-hp ( https://github.com/mattray/knife-hp )
Hide
Permalink
Bryan McLellan [Opscode] added a comment -

I'm marking this as resolved for review. Matt, any reason this isn't ready to be merged into 0.6.14 (2nd release from now)

Show
Bryan McLellan [Opscode] added a comment - I'm marking this as resolved for review. Matt, any reason this isn't ready to be merged into 0.6.14 (2nd release from now)
Hide
Permalink
Bryan McLellan [Opscode] added a comment -

The MAC address used in this plugin isn't in the OUI list but appears to be common to Openstack, not just to HP Cloud. Notably Rackspace is moving to Openstack as well, so this wouldn't work very well.

If there was a reliable MAC prefix here, ideally we would upfactor this code rather than duplicating the EC2 code as well.

I suppose we could use this for detecting Openstack though, or something like it. That becomes an interesting problem; openstack can use different virtualization technology, which we would want to store in node[:virtualization] and could be used by different cloud providers which we use node[:cloud] for. Perhaps we need to expand one of the two. I propose node[:cloud][:system] to be 'openstack' to match node[:virtualization][:system].

Show
Bryan McLellan [Opscode] added a comment - The MAC address used in this plugin isn't in the OUI list but appears to be common to Openstack, not just to HP Cloud. Notably Rackspace is moving to Openstack as well, so this wouldn't work very well. If there was a reliable MAC prefix here, ideally we would upfactor this code rather than duplicating the EC2 code as well. I suppose we could use this for detecting Openstack though, or something like it. That becomes an interesting problem; openstack can use different virtualization technology, which we would want to store in node [:virtualization] and could be used by different cloud providers which we use node [:cloud] for. Perhaps we need to expand one of the two. I propose node [:cloud] [:system] to be 'openstack' to match node [:virtualization] [:system] .
Hide
Permalink
Matt Ray added a comment -

I propose holding off on this technique and use the new /etc/chef/ohai/hints/hp.json technique from CHEF-3160. I'm doing it for knife-openstack right now, I'll add support for knife-hp similarly

Show
Matt Ray added a comment - I propose holding off on this technique and use the new /etc/chef/ohai/hints/hp.json technique from CHEF-3160 . I'm doing it for knife-openstack right now, I'll add support for knife-hp similarly
Hide
Permalink
Matt Ray added a comment -

This is rolled into the fix for OHAI-381

Show
Matt Ray added a comment - This is rolled into the fix for OHAI-381

People

  • Assignee:
    Matt Ray
    Reporter:
    Matthew Macdonald-Wallace
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: