You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by sebgoa <ru...@gmail.com> on 2015/08/12 12:31:25 UTC
Release EC2stack 1.0.0
Hi folks,
I am working towards making a release of EC2stack.
Since it was given to our project we have not made an official release.
I just added a few documentation files, added license headers, notice files, copied over the release script from cloud monkey.
Plus a few other odds and ins.
I don't plan to do any changes to the actual code for now, but I would like to make a 1.0.0 release and then start patching.
How do people feel about this ?
Has anyone used it lately with 4.5.x releases ?
finally, any help to get the Travis runs working again would be good, matter of changing the links I think.
feedback welcome, otherwise I will just cut a release and send a vote thread.
cheers,
-Sebastien
Re: Release EC2stack 1.0.0
Posted by Ian Duffy <ia...@ianduffy.ie>.
@seboga opened a ticket for the coveralls stuff
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10123
I believe the pypi submission doesn't like the readme as an md and it will
render it weirdly on pypi (open to correction on this).
I've added you on the pypi entry so you should be able to upload the latest
binary to there.
On 13 August 2015 at 22:36, Ian Duffy <ia...@ianduffy.ie> wrote:
> > Yes and it seems to work ok with a recent version (1.7.42) of the aws
> cli
> [1] once you tell it to use V2 signature. I have not tried it with the ec2
> cli tools [2].
>
> Awesome! good spot.
>
> We(Myself and Darren) noticed it stopped working with the latest awscli
> due to changes in boto, our workaround due to not having time to work on it
> was just to use an older version. Glad to see you found a better method.
>
> > One thing that would help is to try and figure out a good place to put
> the
> name/internal name/display name fields that are used in Cloudstack.
>
> The language used between Cloudstack and AWS isn't identical. When we were
> making EC2Stack we just tried to use best common sense for
> the conversion of fields.
>
> PrivateDNSName *to me* would be something that one would be able to
> resolve... if displayname.whatever-set-domain.tld is resolvable at some
> point in the system then this change seems sane. Otherwise use a tag.
>
> If you want to do a PR totally happy to review it. its been awhile since I
> worked on ec2stack so my memory is a bit foggy if I remember correctly it
> should just be a case of modifying ec2stack/templates/instances.xml adding
> the appropriate key with value of instance.displayname
>
> On 12 August 2015 at 18:44, Carlos Reategui <ca...@reategui.com> wrote:
>
>> > Has anyone used it lately with 4.5.x releases ?
>> >
>>
>> Yes and it seems to work ok with a recent version (1.7.42) of the aws cli
>> [1] once you tell it to use V2 signature. I have not tried it with the
>> ec2
>> cli tools [2].
>>
>>
>> >
>> > feedback welcome, otherwise I will just cut a release and send a vote
>> > thread.
>> >
>>
>> One thing that would help is to try and figure out a good place to put the
>> name/internal name/display name fields that are used in Cloudstack. Those
>> don't exist as part of the output of describe instances [3] and therefore
>> you get something like the table below which is not terribly helpful
>> unless
>> you know the IP of the machine in question. AWS generally uses tags for
>> things like that. They will prompt you to fill in a Name tag by default in
>> the launch wizard. One possibility for Name could be to stick it in the
>> PrivateDnsName, but not sure about the other 2. Thoughts?
>>
>> thanks,
>> Carlos
>>
>> [1] http://docs.aws.amazon.com/cli/latest/reference/
>> [2]
>>
>> http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/command-reference.html
>> [3]
>>
>> http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html#output
>>
>>
>> Output of describe-instances with table output:
>>
>> ------------------------------------------------------------------
>>
>> | DescribeInstances |
>>
>> +----------------------------------------------------------------+
>>
>> || Reservations ||
>>
>> |+------------------------------------------+-------------------+|
>>
>> || *ReservationId* | *None* ||
>>
>> |+------------------------------------------+-------------------+|
>>
>> ||| Instances |||
>>
>> ||+-------------------+----------------------------------------+||
>>
>> ||| *Hypervisor* | *XenServer* |||
>>
>> ||| *ImageId* | *b4eb47a7-fc58-4b8a-a1d1-c67a475ed452* |||
>>
>> ||| *InstanceId* | *382815c2-4af2-4fa1-852b-5b4c70602005* |||
>>
>> ||| *InstanceType* | *m1.small* |||
>>
>> ||| *KeyName* | |||
>>
>> ||| *LaunchTime* | *2014-09-27T17:40:39-0700* |||
>>
>> ||| *PrivateIpAddress* | *10.110.106.132* |||
>>
>> ||| *PublicIpAddress* | *10.110.106.132* |||
>>
>> ||+-------------------+----------------------------------------+||
>>
>> |||| Placement ||||
>>
>> |||+----------------------------------+-----------------------+|||
>>
>> |||| *AvailabilityZone* | *Sunnyvale* ||||
>>
>> |||| *Tenancy* | *default* ||||
>>
>> |||+----------------------------------+-----------------------+|||
>>
>> |||| State ||||
>>
>> |||+-----------------------+----------------------------------+|||
>>
>> |||| *Code* | *80* ||||
>>
>> |||| *Name* | *stopped* ||||
>>
>> |||+-----------------------+----------------------------------+|||
>>
>
>
Re: Release EC2stack 1.0.0
Posted by Carlos Reategui <cr...@gmail.com>.
Hi Ian,
PrivateDNSName *to me* would be something that one would be able to
> resolve... if displayname.whatever-set-domain.tld is resolvable at some
> point in the system then this change seems sane. Otherwise use a tag.
>
I suggested Name because that is what the hostname gets set to. You can
also resolve that name when dns querying the VR (at least on my basic
network setup). I don't know what display name is used for. It does not
come across in any of the meta-data from the VR.
> If you want to do a PR totally happy to review it. its been awhile since I
> worked on ec2stack so my memory is a bit foggy if I remember correctly it
> should just be a case of modifying ec2stack/templates/instances.xml adding
> the appropriate key with value of instance.displayname
>
I'm out for the next few days but I'll have a look next week and see if I
can figure that out. May be a good solution for now.
cheers
Carlos
Re: Release EC2stack 1.0.0
Posted by Ian Duffy <ia...@ianduffy.ie>.
> Yes and it seems to work ok with a recent version (1.7.42) of the aws cli
[1] once you tell it to use V2 signature. I have not tried it with the ec2
cli tools [2].
Awesome! good spot.
We(Myself and Darren) noticed it stopped working with the latest awscli due
to changes in boto, our workaround due to not having time to work on it was
just to use an older version. Glad to see you found a better method.
> One thing that would help is to try and figure out a good place to put the
name/internal name/display name fields that are used in Cloudstack.
The language used between Cloudstack and AWS isn't identical. When we were
making EC2Stack we just tried to use best common sense for
the conversion of fields.
PrivateDNSName *to me* would be something that one would be able to
resolve... if displayname.whatever-set-domain.tld is resolvable at some
point in the system then this change seems sane. Otherwise use a tag.
If you want to do a PR totally happy to review it. its been awhile since I
worked on ec2stack so my memory is a bit foggy if I remember correctly it
should just be a case of modifying ec2stack/templates/instances.xml adding
the appropriate key with value of instance.displayname
On 12 August 2015 at 18:44, Carlos Reategui <ca...@reategui.com> wrote:
> > Has anyone used it lately with 4.5.x releases ?
> >
>
> Yes and it seems to work ok with a recent version (1.7.42) of the aws cli
> [1] once you tell it to use V2 signature. I have not tried it with the ec2
> cli tools [2].
>
>
> >
> > feedback welcome, otherwise I will just cut a release and send a vote
> > thread.
> >
>
> One thing that would help is to try and figure out a good place to put the
> name/internal name/display name fields that are used in Cloudstack. Those
> don't exist as part of the output of describe instances [3] and therefore
> you get something like the table below which is not terribly helpful unless
> you know the IP of the machine in question. AWS generally uses tags for
> things like that. They will prompt you to fill in a Name tag by default in
> the launch wizard. One possibility for Name could be to stick it in the
> PrivateDnsName, but not sure about the other 2. Thoughts?
>
> thanks,
> Carlos
>
> [1] http://docs.aws.amazon.com/cli/latest/reference/
> [2]
>
> http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/command-reference.html
> [3]
>
> http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html#output
>
>
> Output of describe-instances with table output:
>
> ------------------------------------------------------------------
>
> | DescribeInstances |
>
> +----------------------------------------------------------------+
>
> || Reservations ||
>
> |+------------------------------------------+-------------------+|
>
> || *ReservationId* | *None* ||
>
> |+------------------------------------------+-------------------+|
>
> ||| Instances |||
>
> ||+-------------------+----------------------------------------+||
>
> ||| *Hypervisor* | *XenServer* |||
>
> ||| *ImageId* | *b4eb47a7-fc58-4b8a-a1d1-c67a475ed452* |||
>
> ||| *InstanceId* | *382815c2-4af2-4fa1-852b-5b4c70602005* |||
>
> ||| *InstanceType* | *m1.small* |||
>
> ||| *KeyName* | |||
>
> ||| *LaunchTime* | *2014-09-27T17:40:39-0700* |||
>
> ||| *PrivateIpAddress* | *10.110.106.132* |||
>
> ||| *PublicIpAddress* | *10.110.106.132* |||
>
> ||+-------------------+----------------------------------------+||
>
> |||| Placement ||||
>
> |||+----------------------------------+-----------------------+|||
>
> |||| *AvailabilityZone* | *Sunnyvale* ||||
>
> |||| *Tenancy* | *default* ||||
>
> |||+----------------------------------+-----------------------+|||
>
> |||| State ||||
>
> |||+-----------------------+----------------------------------+|||
>
> |||| *Code* | *80* ||||
>
> |||| *Name* | *stopped* ||||
>
> |||+-----------------------+----------------------------------+|||
>
Re: Release EC2stack 1.0.0
Posted by Carlos Reategui <ca...@reategui.com>.
> Has anyone used it lately with 4.5.x releases ?
>
Yes and it seems to work ok with a recent version (1.7.42) of the aws cli
[1] once you tell it to use V2 signature. I have not tried it with the ec2
cli tools [2].
>
> feedback welcome, otherwise I will just cut a release and send a vote
> thread.
>
One thing that would help is to try and figure out a good place to put the
name/internal name/display name fields that are used in Cloudstack. Those
don't exist as part of the output of describe instances [3] and therefore
you get something like the table below which is not terribly helpful unless
you know the IP of the machine in question. AWS generally uses tags for
things like that. They will prompt you to fill in a Name tag by default in
the launch wizard. One possibility for Name could be to stick it in the
PrivateDnsName, but not sure about the other 2. Thoughts?
thanks,
Carlos
[1] http://docs.aws.amazon.com/cli/latest/reference/
[2]
http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/command-reference.html
[3]
http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html#output
Output of describe-instances with table output:
------------------------------------------------------------------
| DescribeInstances |
+----------------------------------------------------------------+
|| Reservations ||
|+------------------------------------------+-------------------+|
|| *ReservationId* | *None* ||
|+------------------------------------------+-------------------+|
||| Instances |||
||+-------------------+----------------------------------------+||
||| *Hypervisor* | *XenServer* |||
||| *ImageId* | *b4eb47a7-fc58-4b8a-a1d1-c67a475ed452* |||
||| *InstanceId* | *382815c2-4af2-4fa1-852b-5b4c70602005* |||
||| *InstanceType* | *m1.small* |||
||| *KeyName* | |||
||| *LaunchTime* | *2014-09-27T17:40:39-0700* |||
||| *PrivateIpAddress* | *10.110.106.132* |||
||| *PublicIpAddress* | *10.110.106.132* |||
||+-------------------+----------------------------------------+||
|||| Placement ||||
|||+----------------------------------+-----------------------+|||
|||| *AvailabilityZone* | *Sunnyvale* ||||
|||| *Tenancy* | *default* ||||
|||+----------------------------------+-----------------------+|||
|||| State ||||
|||+-----------------------+----------------------------------+|||
|||| *Code* | *80* ||||
|||| *Name* | *stopped* ||||
|||+-----------------------+----------------------------------+|||
Re: Release EC2stack 1.0.0
Posted by Ian Duffy <ia...@ianduffy.ie>.
No problem. I'll look into those. I'd imagine Darren had them on a personal
account or something.
Any idea if we have an asf account on the related sites? If so Will need to
open infra tickets to get them enabled for the ec2stack GitHub mirror.
On Thursday, August 13, 2015, sebgoa <ru...@gmail.com> wrote:
>
> On Aug 13, 2015, at 12:00 AM, Ian Duffy <ian@ianduffy.ie <javascript:;>>
> wrote:
>
> > Hey Sebastien,
> >
> > Thank you for doing this.
> >
> > If there's any small jobs I can help out let me know, I'm allowed to work
> > on this type of stuff again once Friday the 14th passes.
> >
>
> we are missing a few badges in the readme. I think we had coveralls at one
> point and that fury thing…not sure what that is.
>
> > On Wednesday, August 12, 2015, sebgoa <runseb@gmail.com <javascript:;>>
> wrote:
> >
> >>
> >> On Aug 12, 2015, at 12:31 PM, sebgoa <runseb@gmail.com <javascript:;>
> <javascript:;>>
> >> wrote:
> >>
> >>> Hi folks,
> >>>
> >>> I am working towards making a release of EC2stack.
> >>> Since it was given to our project we have not made an official release.
> >>>
> >>> I just added a few documentation files, added license headers, notice
> >> files, copied over the release script from cloud monkey.
> >>> Plus a few other odds and ins.
> >>>
> >>> I don't plan to do any changes to the actual code for now, but I would
> >> like to make a 1.0.0 release and then start patching.
> >>>
> >>> How do people feel about this ?
> >>> Has anyone used it lately with 4.5.x releases ?
> >>>
> >>> finally, any help to get the Travis runs working again would be good,
> >> matter of changing the links I think.
> >>>
> >>
> >> FWIW, I fixed the Travis build , we are green :)
> >>
> >> https://github.com/apache/cloudstack-ec2stack
> >>
> >>> feedback welcome, otherwise I will just cut a release and send a vote
> >> thread.
> >>>
> >>> cheers,
> >>>
> >>> -Sebastien
> >>
> >>
>
>
Re: Release EC2stack 1.0.0
Posted by sebgoa <ru...@gmail.com>.
On Aug 13, 2015, at 12:00 AM, Ian Duffy <ia...@ianduffy.ie> wrote:
> Hey Sebastien,
>
> Thank you for doing this.
>
> If there's any small jobs I can help out let me know, I'm allowed to work
> on this type of stuff again once Friday the 14th passes.
>
we are missing a few badges in the readme. I think we had coveralls at one point and that fury thing…not sure what that is.
> On Wednesday, August 12, 2015, sebgoa <ru...@gmail.com> wrote:
>
>>
>> On Aug 12, 2015, at 12:31 PM, sebgoa <runseb@gmail.com <javascript:;>>
>> wrote:
>>
>>> Hi folks,
>>>
>>> I am working towards making a release of EC2stack.
>>> Since it was given to our project we have not made an official release.
>>>
>>> I just added a few documentation files, added license headers, notice
>> files, copied over the release script from cloud monkey.
>>> Plus a few other odds and ins.
>>>
>>> I don't plan to do any changes to the actual code for now, but I would
>> like to make a 1.0.0 release and then start patching.
>>>
>>> How do people feel about this ?
>>> Has anyone used it lately with 4.5.x releases ?
>>>
>>> finally, any help to get the Travis runs working again would be good,
>> matter of changing the links I think.
>>>
>>
>> FWIW, I fixed the Travis build , we are green :)
>>
>> https://github.com/apache/cloudstack-ec2stack
>>
>>> feedback welcome, otherwise I will just cut a release and send a vote
>> thread.
>>>
>>> cheers,
>>>
>>> -Sebastien
>>
>>
Re: Release EC2stack 1.0.0
Posted by Ian Duffy <ia...@ianduffy.ie>.
Hey Sebastien,
Thank you for doing this.
If there's any small jobs I can help out let me know, I'm allowed to work
on this type of stuff again once Friday the 14th passes.
On Wednesday, August 12, 2015, sebgoa <ru...@gmail.com> wrote:
>
> On Aug 12, 2015, at 12:31 PM, sebgoa <runseb@gmail.com <javascript:;>>
> wrote:
>
> > Hi folks,
> >
> > I am working towards making a release of EC2stack.
> > Since it was given to our project we have not made an official release.
> >
> > I just added a few documentation files, added license headers, notice
> files, copied over the release script from cloud monkey.
> > Plus a few other odds and ins.
> >
> > I don't plan to do any changes to the actual code for now, but I would
> like to make a 1.0.0 release and then start patching.
> >
> > How do people feel about this ?
> > Has anyone used it lately with 4.5.x releases ?
> >
> > finally, any help to get the Travis runs working again would be good,
> matter of changing the links I think.
> >
>
> FWIW, I fixed the Travis build , we are green :)
>
> https://github.com/apache/cloudstack-ec2stack
>
> > feedback welcome, otherwise I will just cut a release and send a vote
> thread.
> >
> > cheers,
> >
> > -Sebastien
>
>
Re: Release EC2stack 1.0.0
Posted by sebgoa <ru...@gmail.com>.
On Aug 12, 2015, at 12:31 PM, sebgoa <ru...@gmail.com> wrote:
> Hi folks,
>
> I am working towards making a release of EC2stack.
> Since it was given to our project we have not made an official release.
>
> I just added a few documentation files, added license headers, notice files, copied over the release script from cloud monkey.
> Plus a few other odds and ins.
>
> I don't plan to do any changes to the actual code for now, but I would like to make a 1.0.0 release and then start patching.
>
> How do people feel about this ?
> Has anyone used it lately with 4.5.x releases ?
>
> finally, any help to get the Travis runs working again would be good, matter of changing the links I think.
>
FWIW, I fixed the Travis build , we are green :)
https://github.com/apache/cloudstack-ec2stack
> feedback welcome, otherwise I will just cut a release and send a vote thread.
>
> cheers,
>
> -Sebastien
Re: Release EC2stack 1.0.0
Posted by Rohit Yadav <ro...@shapeblue.com>.
On 12-Aug-2015, at 4:01 pm, sebgoa <ru...@gmail.com>> wrote:
How do people feel about this ?
Has anyone used it lately with 4.5.x releases ?
I had test ec2stack with 4.5.1 release and help set it up for a pre-production environment as well.
Last time I checked I was able to work awscli with it, not to mention how painless it was compared to awsapi (which btw did not work with 4.5.x, for me).
Regards,
Rohit Yadav
Software Architect, ShapeBlue
[cid:9DD97B41-04C5-45F0-92A7-951F3E962F7A]
M. +91 88 262 30892 | rohit.yadav@shapeblue.com<ma...@shapeblue.com>
Blog: bhaisaab.org<http://bhaisaab.org> | Twitter: @_bhaisaab
Find out more about ShapeBlue and our range of CloudStack related services
IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge - rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.