Update AWS Provisioner

[mafernando]

• [x] Add the following attributes to AWS provisioning questions
  • [x] VPC
  • [x] Subnet
  • [x] Security Group
• [x] Add ability to provision more than t1.micros
  • Solution: Need to specify flavor_id attribute instead instance_id for size of instance
• [x] Add product types for the following
  • [x] VPC
  • [x] Subnet
  • [x] Security Group
• [x] Add ability to add EBS storage (maybe as a new product type?)
• [x] Cut new jellyfish-fog gem
  • [x] Verify AWS provisioning of all product types
  • [x] Push updated gem to RubyGems
  • [x] Update API lockfile with reference to update gem
• Need to decide what kinds of options we want to provide beyond the basic for the newly added product types - to be revisited later

[mafernando]

References:

• ami-0bc9d462 Community CentOS6.5_HVM_SR-IOV_ixgbevf-2.14.2 AMI
• ami-1ccae774 Amazon Linux AMI 2015.03.0 x86_64 PV EBS
• security group attributes fog aws
• how to add existing ebs volumes
• fog compute vpc model v1
• fog compue vpc model v2
• convert json to ruby hash
• create subnet fog
• create security subgroup
• network vs broadcast id & cidr
• create ebs with fog
• delete rds with fog

[mafernando]

Issues:

• configuration details may need to be revisited back in jellyfish api. the issue here is that default options in details need to be nil not empty string. See AWS Infrastructure provisioner.
• not sure if connection.delete_vpc will remove all associated resources with the VPC, may want to look into this
• the object mocked in specs does not match the object generated for Fog corresponding to a provision response. this causes problems with accessing attributes using symbols or strings for keys.
  • _solution: since mock object doesn't serialize the payloadresponse as JSON, manually add that step in before retirement spec
  • [x] follow-up: need to revisit AWS Infrastructure provisioning and make sure that the payload is stored correctly. When the response is converted to JSON, the any symbol keys contained therein will be flattened and will need to be referenced using strings.

[mafernando]

Examples:

• create a vpc on AWS (see method here)

  [20] pry(#<Jellyfish::Fog::AWS::VPC>)> connection.create_vpc(details['cidr_block'])
  => #<Excon::Response:0x007fe6767abe08
  @body="",
  @data=
  {:body=>{"vpcSet"=>[{"tagSet"=>{}, "vpcId"=>"vpc-b8053cdd", "state"=>"pending", "cidrBlock"=>"10.0.0.0/16", "dhcpOptionsId"=>"dopt-0ce6fc6e"}], "requestId"=>"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"},
  :headers=>{"Content-Type"=>"text/xml;charset=UTF-8", "Vary"=>"Accept-Encoding", "Date"=>"Mon, 01 Jun 2015 19:57:53 GMT", "Server"=>"AmazonEC2"},
  :status=>200,
  :status_line=>"HTTP/1.1 200 OK\r\n",
  :reason_phrase=>"OK",
  :remote_ip=>"ZZZ.ZZZ.ZZZ.Z",
  :local_port=>#####,
  :local_address=>"YYY.YYY.YYY.YYY"},
  @headers={"Content-Type"=>"text/xml;charset=UTF-8", "Vary"=>"Accept-Encoding", "Date"=>"Mon, 01 Jun 2015 19:57:53 GMT", "Server"=>"AmazonEC2"},
  @local_address="YYY.YYY.YYY.YYY",
  @local_port=60972,
  @remote_ip="ZZZ.ZZZ.ZZZ.Z",
  @status=200>
  [21] pry(#<Jellyfish::Fog::AWS::VPC>)> connection.vpcs
  => [  <Fog::Compute::AWS::VPC
  id="vpc-XXXXXXXX",
  state="available",
  cidr_block="10.0.0.0/16",
  dhcp_options_id="dopt-0ce6fc6e",
  tags={},
  tenancy="default"
  >]

[mafernando]

Closed with 03b778e5877aed42f8ccdbe2e656b3ab089d8bf6