details parameter of registerTemplate API

[Atsushi Sasaki]

Hi,

I used details parameter of registerTemplate API to set keyboard=jp.

I use following format to pass argument as CLOUDSTACK-4719 says.

details[0].keyboard=jp

https://issues.apache.org/jira/browse/CLOUDSTACK-4719

Most of API parameters that accept map type seems to accept like following
format, although details of registerTemplate can't accept it as expected

detais[0].key=keyboard&details[0].value=jp

Why details parameter of registerTemplate uses different format from most
of the other parameters?

It is hard to use API and make library correctly because we can't check
which format is used in advance.
If possible, I want to use same format in all case.

Atsushi Sasaki

RE: How to set limit on “Acquire New IP” for isolated network

[Sonali Jadhav]

Thanks, that helped :) 

/Sonali

-Original Message-
From: Somesh Naidu [mailto:somesh.na...@citrix.com] 
Sent: Tuesday, February 10, 2015 8:26 PM
To: users@cloudstack.apache.org
Subject: RE: How to set limit on “Acquire New IP” for isolated network

Try using global config max.account.public.ips if you want to set limit on all 
accounts. You could override the limits for a specific account/s by updating 
the limits for that account/s.

Regards,
Somesh

-Original Message-
From: Sonali Jadhav [mailto:son...@servercentralen.se] 
Sent: Tuesday, February 10, 2015 5:56 AM
To: users@cloudstack.apache.org
Subject: RE: How to set limit on “Acquire New IP” for isolated network

Yes I know that one, I had set it to 1 from beginning but still user can 
acquire unlimited IPs. So I thought For isolated network setting might be 
different. 

/Sonali

-Original Message-
From: Jayapal Reddy Uradi [mailto:jayapalreddy.ur...@citrix.com] 
Sent: Tuesday, February 10, 2015 4:16 PM
To: 
Subject: Re: How to set limit on “Acquire New IP” for isolated network

Hi Sonali,

In global settings we have the below option to control the public ips use.
max.project.public.ips  The default maximum number of public IPs that can be 
consumed by a project


Thanks,
Jayapal

On 10-Feb-2015, at 4:11 PM, Sonali Jadhav 
mailto:son...@servercentralen.se>>
 wrote:

Hi,

There is one project, created new isolated network for that project.  I 
observed that user can “Acquire New IP” for isolated network.  How do we set 
limit on how much IP users can acquire ? Because this way, user can consume any 
number of public IPs they want.

Yours sincerely,

Sonali Jadhav | System Administrator
Nordiska Servercentralen
Skype ID: sonali.jadhav.sj
E-mail: 
son...@servercentralen.se

RE: How to shutdown CS?

[Glenn Wagner]

Good day,

The best way to do this is too , put  your primary storage into maintenance 
mode first, secondly disable your zone so your system VM's don't automatically 
try restart
You system VM's will start shutting down.




Glenn Wagner
Senior Consultant, South Africa



M: +27 73 917 4

glenn.wag...@shapeblue.com | www.shapeblue.com | Twitter:@shapeBlue

-Original Message-
From: create...@gmail.com [mailto:create...@gmail.com] On Behalf Of Carlos 
Reategui
Sent: 11 February 2015 01:48 AM
To: users@cloudstack.apache.org
Subject: Re: How to shutdown CS?

Not sure what the proper way to do so, but what I have done which has worked 
for me is as follows.  The basic premise is that the management server DB is 
representative of the current state of the system.  Therefore when you bring 
things back online, if they match the state in the DB then CS will have no idea 
that you shut it down.

In my case I try to shutdown all the running instances from within CS.
Then stop the management server.  The next step is critical.  I use xenserver 
so I pull up XenCenter and pause/stop any remaining instances (e.g. system 
VMs).  Then I proceed to shutdown the hosts, storage and the the management 
server host (make sure CS will not auto start).  When I bring things back 
online, I start all the instances that I stopped/paused outside of CS and make 
sure everything looks the way it did when I stopped the management server.  
Only then do I start the management server process.



On Tue, Feb 10, 2015 at 1:42 PM, José Egas López 
wrote:

> Hi, I want to know how to properly shutdown the entire CloudStack
> Infraestructure, I will upgrade resources of the main host.
>
>
>
>
>
> Regards,
>
>
>
> José
>
>
>
>
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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.

Re: How to shutdown CS?

[Carlos Reategui]

Not sure what the proper way to do so, but what I have done which has
worked for me is as follows.  The basic premise is that the management
server DB is representative of the current state of the system.  Therefore
when you bring things back online, if they match the state in the DB then
CS will have no idea that you shut it down.

In my case I try to shutdown all the running instances from within CS.
Then stop the management server.  The next step is critical.  I use
xenserver so I pull up XenCenter and pause/stop any remaining instances
(e.g. system VMs).  Then I proceed to shutdown the hosts, storage and the
the management server host (make sure CS will not auto start).  When I
bring things back online, I start all the instances that I stopped/paused
outside of CS and make sure everything looks the way it did when I stopped
the management server.  Only then do I start the management server process.



On Tue, Feb 10, 2015 at 1:42 PM, José Egas López 
wrote:

> Hi, I want to know how to properly shutdown the entire CloudStack
> Infraestructure, I will upgrade resources of the main host.
>
>
>
>
>
> Regards,
>
>
>
> José
>
>
>
>

RE: How to shutdown CS?

[Somesh Naidu]

Yes.

-somesh

Sent from my Verizon Wireless 4G LTE DROID
On Feb 10, 2015 6:06 PM, =?ISO-8859-1?Q?Jos=E9_Egas_L=F3pez?= 
 wrote:
After I disable the zone, do I have to shut down the sysVMs manually?

Regards,
José

-Mensaje original-
De: Somesh Naidu [mailto:somesh.na...@citrix.com]
Enviado el: martes, 10 de febrero de 2015 17:27
Para: users@cloudstack.apache.org
Asunto: RE: How to shutdown CS?

Well, when you bring down the hypervisor and storage, you could shutdown the
system VMs along with the guest VMs.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Tuesday, February 10, 2015 5:06 PM
To: users@cloudstack.apache.org
Subject: RE: How to shutdown CS?

Ok, thanks, and what about de sysVMs?


Regards,

José

-Mensaje original-
De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: martes, 10 de
febrero de 2015 16:52
Para: users@cloudstack.apache.org
Asunto: RE: How to shutdown CS?

When you say "entire Cloudstack infrastructure" do you mean all hypervisor
hosts, guests, storage servers, etc?

Ideally, from a CS perspective, stopping the management service (all
servers) should suffice. If you want to be extra careful, you could first
disable all your zones from the UI, wait for all currently running
operations to finish and then stop management service. Beyond that, you
could follow the guidelines from the hypervisor and storage vendors to pull
the services down on those.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Tuesday, February 10, 2015 4:43 PM
To: users@cloudstack.apache.org
Subject: How to shutdown CS?

Hi, I want to know how to properly shutdown the entire CloudStack
Infraestructure, I will upgrade resources of the main host.





Regards,



José

RE: How to shutdown CS?

[José Egas López]

After I disable the zone, do I have to shut down the sysVMs manually?

Regards,
José

-Mensaje original-
De: Somesh Naidu [mailto:somesh.na...@citrix.com] 
Enviado el: martes, 10 de febrero de 2015 17:27
Para: users@cloudstack.apache.org
Asunto: RE: How to shutdown CS?

Well, when you bring down the hypervisor and storage, you could shutdown the
system VMs along with the guest VMs.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Tuesday, February 10, 2015 5:06 PM
To: users@cloudstack.apache.org
Subject: RE: How to shutdown CS?

Ok, thanks, and what about de sysVMs?


Regards,

José

-Mensaje original-
De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: martes, 10 de
febrero de 2015 16:52
Para: users@cloudstack.apache.org
Asunto: RE: How to shutdown CS?

When you say "entire Cloudstack infrastructure" do you mean all hypervisor
hosts, guests, storage servers, etc?

Ideally, from a CS perspective, stopping the management service (all
servers) should suffice. If you want to be extra careful, you could first
disable all your zones from the UI, wait for all currently running
operations to finish and then stop management service. Beyond that, you
could follow the guidelines from the hypervisor and storage vendors to pull
the services down on those.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Tuesday, February 10, 2015 4:43 PM
To: users@cloudstack.apache.org
Subject: How to shutdown CS?

Hi, I want to know how to properly shutdown the entire CloudStack
Infraestructure, I will upgrade resources of the main host.

 

 

Regards,

 

José

 

RE: How to shutdown CS?

[Somesh Naidu]

Well, when you bring down the hypervisor and storage, you could shutdown the 
system VMs along with the guest VMs.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com] 
Sent: Tuesday, February 10, 2015 5:06 PM
To: users@cloudstack.apache.org
Subject: RE: How to shutdown CS?

Ok, thanks, and what about de sysVMs?


Regards,

José

-Mensaje original-
De: Somesh Naidu [mailto:somesh.na...@citrix.com] 
Enviado el: martes, 10 de febrero de 2015 16:52
Para: users@cloudstack.apache.org
Asunto: RE: How to shutdown CS?

When you say "entire Cloudstack infrastructure" do you mean all hypervisor
hosts, guests, storage servers, etc?

Ideally, from a CS perspective, stopping the management service (all
servers) should suffice. If you want to be extra careful, you could first
disable all your zones from the UI, wait for all currently running
operations to finish and then stop management service. Beyond that, you
could follow the guidelines from the hypervisor and storage vendors to pull
the services down on those.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Tuesday, February 10, 2015 4:43 PM
To: users@cloudstack.apache.org
Subject: How to shutdown CS?

Hi, I want to know how to properly shutdown the entire CloudStack
Infraestructure, I will upgrade resources of the main host.

 

 

Regards,

 

José

 

RE: How to shutdown CS?

[José Egas López]

Ok, thanks, and what about de sysVMs?


Regards,

José

-Mensaje original-
De: Somesh Naidu [mailto:somesh.na...@citrix.com] 
Enviado el: martes, 10 de febrero de 2015 16:52
Para: users@cloudstack.apache.org
Asunto: RE: How to shutdown CS?

When you say "entire Cloudstack infrastructure" do you mean all hypervisor
hosts, guests, storage servers, etc?

Ideally, from a CS perspective, stopping the management service (all
servers) should suffice. If you want to be extra careful, you could first
disable all your zones from the UI, wait for all currently running
operations to finish and then stop management service. Beyond that, you
could follow the guidelines from the hypervisor and storage vendors to pull
the services down on those.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Tuesday, February 10, 2015 4:43 PM
To: users@cloudstack.apache.org
Subject: How to shutdown CS?

Hi, I want to know how to properly shutdown the entire CloudStack
Infraestructure, I will upgrade resources of the main host.

 

 

Regards,

 

José

 

RE: Virtual Router not resolving local names

[Somesh Naidu]

Is your DNS server able to resolve the names? Did you test pointing a box 
directly to the DNS and see if these names resolve via the DNS?

Regards,
Somesh


-Original Message-
From: Osay Osman Yuuni [mailto:oyu...@gmail.com] 
Sent: Tuesday, February 10, 2015 1:13 PM
To: users@cloudstack.apache.org
Subject: Virtual Router not resolving local names

Hi,

My virtual router isn't resolving both local and public names though I
configured local DNS1 and DNS2 to point to my local DNS server.  Instances
have resolv.conf showing the VR interface as DNS1 and a public IP as DNS2.
I'm not sure what is going on.  I have to change the resolv.conf on the
instance to be able to work but this gets changed back.

Any clues?

RE: How to shutdown CS?

[Somesh Naidu]

When you say "entire Cloudstack infrastructure" do you mean all hypervisor 
hosts, guests, storage servers, etc?

Ideally, from a CS perspective, stopping the management service (all servers) 
should suffice. If you want to be extra careful, you could first disable all 
your zones from the UI, wait for all currently running operations to finish and 
then stop management service. Beyond that, you could follow the guidelines from 
the hypervisor and storage vendors to pull the services down on those.

Regards,
Somesh


-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com] 
Sent: Tuesday, February 10, 2015 4:43 PM
To: users@cloudstack.apache.org
Subject: How to shutdown CS?

Hi, I want to know how to properly shutdown the entire CloudStack
Infraestructure, I will upgrade resources of the main host.

 

 

Regards,

 

José

 

How to shutdown CS?

[José Egas López]

Hi, I want to know how to properly shutdown the entire CloudStack
Infraestructure, I will upgrade resources of the main host.

 

 

Regards,

 

José

 

Virtual Router not resolving local names

[Osay Osman Yuuni]

Hi,

My virtual router isn't resolving both local and public names though I
configured local DNS1 and DNS2 to point to my local DNS server.  Instances
have resolv.conf showing the VR interface as DNS1 and a public IP as DNS2.
I'm not sure what is going on.  I have to change the resolv.conf on the
instance to be able to work but this gets changed back.

Any clues?

Re: Docker Support?

[Osay Osman Yuuni]

Feedback from @svanharmelen  just rebased
the PR so it should be good now  I've tried it and it works.  Will let
you know how it works out.

On 10 February 2015 at 16:03, Osay Osman Yuuni  wrote:

> Hi Seb and Nux!,
> I've tried to patch the docker machine using pull request 425 but this
> fails with the following errors:
>
> Applying: cloudstack driver
> error: patch failed: README.md:266
> error: README.md: patch does not apply
> error: patch failed: commands.go:16
> error: commands.go: patch does not apply
> Patch failed at 0001 cloudstack driver
> The copy of the patch that failed is found in:
>/home/core/machine/.git/rebase-apply/patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> Has anyone successfully applied the patch?  I'm actually running this on
> one of the coreos instances I created.  I remember successfully running
> this on a CentOS 6.6 VM on which I installed Docker.  Seems very wierd
> though.
>
> TIA
>
> On 5 February 2015 at 11:53, sebgoa  wrote:
>
>>
>> On Feb 5, 2015, at 10:37 AM, Nux!  wrote:
>>
>> > Where might these patches be? (links)
>>
>> https://github.com/docker/machine/pull/20
>>
>> https://github.com/docker/machine/pull/425
>>
>>
>>
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
>> >
>> > - Original Message -
>> >> From: "sebgoa" 
>> >> To: users@cloudstack.apache.org
>> >> Sent: Thursday, 5 February, 2015 09:07:02
>> >> Subject: Re: Docker Support?
>> >
>> >> On Feb 5, 2015, at 9:07 AM, cs user  wrote:
>> >>
>> >>> Hi Osay,
>> >>>
>> >>> I'd be really interested to hear about how you get on with the
>> Cloudstack
>> >>> Driver for Docker Machine, using the CoreOS template.
>> >>>
>> >>
>> >> FYI, there are two pull requests in Docker machine that support
>> cloudstack.
>> >> One for exoscale which can be used with basic zones, it works just
>> fine.
>> >> One for advanced zone from Sander @schuberg philis, also works
>> >>
>> >> Unfortunately the docker team has not merged them yet…hopefully soon.
>> >>
>> >> if you git clone docker machine and applied the patches by hand , you
>> will be
>> >> good to go.
>> >>
>> >>> Cheers! :-)
>> >>>
>> >>> On Thu, Feb 5, 2015 at 6:20 AM, Osay Osman Yuuni 
>> wrote:
>> >>>
>>  Thanks Lucian.  Actually I'm running this off of Xenserver.  I'll
>> try with
>>  "Other PV 64bit" and perhaps Ubuntu 12.04 to see the differences.
>>  Cheers,
>> 
>>  Osay
>> 
>>  On 5 February 2015 at 00:26, Nux!  wrote:
>> 
>> > On KVM "Other PV 64bit" will give you VirtIO (paravirt) disk and
>> network
>> > which give you the best performance. You should always aim to use
>> VirtIO,
>> > even with FreeBSD or Windows (though drivers will be needed for this
>>  one).
>> >
>> > CentOS/Debian/Ubuntu profiles might work, too, but I think at this
>> stage
>> > they don't give you anything extra.
>> >
>> >
>> > Lucian
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
>> >
>> > - Original Message -
>> >> From: "Andrei Mikhailovsky" 
>> >> To: users@cloudstack.apache.org
>> >> Sent: Wednesday, 4 February, 2015 21:26:28
>> >> Subject: Re: Docker Support?
>> >
>> >> Osay,
>> >>
>> >> You might want to try other OS types that support PV, like Other PV
>> > (64bit) or
>> >> even one of the Linux distros like Ubuntu 12.04 (64bit). I think
>> disk
>> >> performance might improve.
>> >>
>> >> Andrei
>> >>
>> >> - Original Message -
>> >>
>> >>> From: "Osay Osman Yuuni" 
>> >>> To: users@cloudstack.apache.org
>> >>> Sent: Wednesday, 4 February, 2015 6:57:51 PM
>> >>> Subject: Re: Docker Support?
>> >>
>> >>> Andrei,
>> >>> I specified Other (64 bit).
>> >>
>> >>> Osay
>> >>
>> >>> On 4 February 2015 at 18:00, Andrei Mikhailovsky <
>> and...@arhont.com>
>> >>> wrote:
>> >>
>>  Osay, what OS Type did you specify when you've uploaded the
>>  template to
>>  your acs?
>> 
>>  Thanks
>> 
>>  Andrei
>> 
>>  - Original Message -
>> 
>> > From: "Osay Osman Yuuni" 
>> > To: users@cloudstack.apache.org
>> > Sent: Wednesday, 4 February, 2015 3:24:16 PM
>> > Subject: Re: Docker Support?
>> 
>> > Hi Lucian and others. Thanks very much to this. By following
>> your
>> > suggestions I now have this working like snake oil. Like you
>> > mentioned
>> > this works great out of the box. I'm now heading off to github
>> to
>> > download
>> > the cloudstack enabled machine program to 

Re: Connection issue with the master

[Salvatore Sciacco]

Hi Jaypal,

in the table configuration I see this field:
ssl.keystore
"SSL Keystore for the management servers"

Do you mean I need to null these values?

Thanks again

S.


2015-02-10 10:12 GMT+01:00 Salvatore Sciacco :

> Also, I'd like to understand why some agent connect just fine
> 2015-02-10 07:07:02,179 INFO  [utils.nio.NioClient] (Agent-Selector:null)
> Connecting to 192.168.11.9:8250
> 2015-02-10 07:07:07,318 INFO  [utils.nio.NioClient] (Agent-Selector:null)
> SSL: Handshake done
> 2015-02-10 07:07:07,319 INFO  [utils.nio.NioClient] (Agent-Selector:null)
> Connected to 192.168.11.9:8250
>
>
>
> 2015-02-10 10:05 GMT+01:00 Salvatore Sciacco :
>
>> Hi Jayapal,
>>
>> do you mean the keystore in /etc/cloudstack/management or the ssl setting
>> in the config?
>>
>> I already tried removing the keystore but the same was generated
>> (copied?) in place of the existing.
>>
>> Thank you very much!
>>
>> S.
>>
>> 2015-02-10 9:53 GMT+01:00 Jayapal Reddy Uradi <
>> jayapalreddy.ur...@citrix.com>:
>>
>>> Hi,
>>>
>>> This issue is related to ssl keys.
>>> Can you remove the keys and try restarting MS and recreate systemvms.
>>>
>>> Thanks,
>>> Jayapal
>>> On 10-Feb-2015, at 1:52 PM, Salvatore Sciacco 
>>>  wrote:
>>>
>>> > Hi,
>>> >
>>> > I have a few hosts and the systemvm (console proxy) which stopped
>>> > connecting to the master with ssl error:
>>> >
>>> > 2015-02-10 08:43:46,057 INFO  [cloud.agent.Agent]
>>> (Agent-Handler-4:null)
>>> > Reconnecting...
>>> > 2015-02-10 08:43:46,058 INFO  [utils.nio.NioClient]
>>> (Agent-Selector:null)
>>> > Connecting to 111.11.1.1:8250
>>> > 2015-02-10 08:43:56,191 ERROR [utils.nio.NioConnection]
>>> > (Agent-Selector:null) Unable to initialize the threads.
>>> > java.io.IOException: SSL: Fail to init SSL! java.io.IOException:
>>> Connection
>>> > closed with -1 on reading size.
>>> >at com.cloud.utils.nio.NioClient.init(NioClient.java:87)
>>> >at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
>>> >at java.lang.Thread.run(Thread.java:745)
>>> >
>>> >
>>> >
>>> > anybody can sugggest how I can debug the SSL layer? Cients are able to
>>> > connect to the port 8250, but they are disconnected just after the
>>> > connection is established.
>>> >
>>> > Thank you very much
>>> >
>>> > S.
>>>
>>>
>>
>

RE: How to set limit on “Acquire New IP” for isolated network

[Somesh Naidu]

Try using global config max.account.public.ips if you want to set limit on all 
accounts. You could override the limits for a specific account/s by updating 
the limits for that account/s.

Regards,
Somesh

-Original Message-
From: Sonali Jadhav [mailto:son...@servercentralen.se] 
Sent: Tuesday, February 10, 2015 5:56 AM
To: users@cloudstack.apache.org
Subject: RE: How to set limit on “Acquire New IP” for isolated network

Yes I know that one, I had set it to 1 from beginning but still user can 
acquire unlimited IPs. So I thought For isolated network setting might be 
different. 

/Sonali

-Original Message-
From: Jayapal Reddy Uradi [mailto:jayapalreddy.ur...@citrix.com] 
Sent: Tuesday, February 10, 2015 4:16 PM
To: 
Subject: Re: How to set limit on “Acquire New IP” for isolated network

Hi Sonali,

In global settings we have the below option to control the public ips use.
max.project.public.ips  The default maximum number of public IPs that can be 
consumed by a project


Thanks,
Jayapal

On 10-Feb-2015, at 4:11 PM, Sonali Jadhav 
mailto:son...@servercentralen.se>>
 wrote:

Hi,

There is one project, created new isolated network for that project.  I 
observed that user can “Acquire New IP” for isolated network.  How do we set 
limit on how much IP users can acquire ? Because this way, user can consume any 
number of public IPs they want.

Yours sincerely,

Sonali Jadhav | System Administrator
Nordiska Servercentralen
Skype ID: sonali.jadhav.sj
E-mail: 
son...@servercentralen.se

Re: Docker Support?

[Osay Osman Yuuni]

Hi Seb and Nux!,
I've tried to patch the docker machine using pull request 425 but this
fails with the following errors:

Applying: cloudstack driver
error: patch failed: README.md:266
error: README.md: patch does not apply
error: patch failed: commands.go:16
error: commands.go: patch does not apply
Patch failed at 0001 cloudstack driver
The copy of the patch that failed is found in:
   /home/core/machine/.git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Has anyone successfully applied the patch?  I'm actually running this on
one of the coreos instances I created.  I remember successfully running
this on a CentOS 6.6 VM on which I installed Docker.  Seems very wierd
though.

TIA

On 5 February 2015 at 11:53, sebgoa  wrote:

>
> On Feb 5, 2015, at 10:37 AM, Nux!  wrote:
>
> > Where might these patches be? (links)
>
> https://github.com/docker/machine/pull/20
>
> https://github.com/docker/machine/pull/425
>
>
>
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "sebgoa" 
> >> To: users@cloudstack.apache.org
> >> Sent: Thursday, 5 February, 2015 09:07:02
> >> Subject: Re: Docker Support?
> >
> >> On Feb 5, 2015, at 9:07 AM, cs user  wrote:
> >>
> >>> Hi Osay,
> >>>
> >>> I'd be really interested to hear about how you get on with the
> Cloudstack
> >>> Driver for Docker Machine, using the CoreOS template.
> >>>
> >>
> >> FYI, there are two pull requests in Docker machine that support
> cloudstack.
> >> One for exoscale which can be used with basic zones, it works just fine.
> >> One for advanced zone from Sander @schuberg philis, also works
> >>
> >> Unfortunately the docker team has not merged them yet…hopefully soon.
> >>
> >> if you git clone docker machine and applied the patches by hand , you
> will be
> >> good to go.
> >>
> >>> Cheers! :-)
> >>>
> >>> On Thu, Feb 5, 2015 at 6:20 AM, Osay Osman Yuuni 
> wrote:
> >>>
>  Thanks Lucian.  Actually I'm running this off of Xenserver.  I'll try
> with
>  "Other PV 64bit" and perhaps Ubuntu 12.04 to see the differences.
>  Cheers,
> 
>  Osay
> 
>  On 5 February 2015 at 00:26, Nux!  wrote:
> 
> > On KVM "Other PV 64bit" will give you VirtIO (paravirt) disk and
> network
> > which give you the best performance. You should always aim to use
> VirtIO,
> > even with FreeBSD or Windows (though drivers will be needed for this
>  one).
> >
> > CentOS/Debian/Ubuntu profiles might work, too, but I think at this
> stage
> > they don't give you anything extra.
> >
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Andrei Mikhailovsky" 
> >> To: users@cloudstack.apache.org
> >> Sent: Wednesday, 4 February, 2015 21:26:28
> >> Subject: Re: Docker Support?
> >
> >> Osay,
> >>
> >> You might want to try other OS types that support PV, like Other PV
> > (64bit) or
> >> even one of the Linux distros like Ubuntu 12.04 (64bit). I think
> disk
> >> performance might improve.
> >>
> >> Andrei
> >>
> >> - Original Message -
> >>
> >>> From: "Osay Osman Yuuni" 
> >>> To: users@cloudstack.apache.org
> >>> Sent: Wednesday, 4 February, 2015 6:57:51 PM
> >>> Subject: Re: Docker Support?
> >>
> >>> Andrei,
> >>> I specified Other (64 bit).
> >>
> >>> Osay
> >>
> >>> On 4 February 2015 at 18:00, Andrei Mikhailovsky <
> and...@arhont.com>
> >>> wrote:
> >>
>  Osay, what OS Type did you specify when you've uploaded the
>  template to
>  your acs?
> 
>  Thanks
> 
>  Andrei
> 
>  - Original Message -
> 
> > From: "Osay Osman Yuuni" 
> > To: users@cloudstack.apache.org
> > Sent: Wednesday, 4 February, 2015 3:24:16 PM
> > Subject: Re: Docker Support?
> 
> > Hi Lucian and others. Thanks very much to this. By following your
> > suggestions I now have this working like snake oil. Like you
> > mentioned
> > this works great out of the box. I'm now heading off to github to
> > download
> > the cloudstack enabled machine program to start some serious
> > work.
> > Great
> > work and thanks for sharing the template and suggestions.
> 
> > Cheers,
> 
> > Osay
> 
> > PS: I never gave cloudmonkey a thought but after this I think I'm
> > going to
> > consign the web gui to very mundane tasks.
> 
> > On 3 February 2015 at 21:32, Nux!  wrote:
> >>>

RE: How to set limit on “Acquire New IP” for isolated network

[Sonali Jadhav]

Yes I know that one, I had set it to 1 from beginning but still user can 
acquire unlimited IPs. So I thought For isolated network setting might be 
different. 

/Sonali

-Original Message-
From: Jayapal Reddy Uradi [mailto:jayapalreddy.ur...@citrix.com] 
Sent: Tuesday, February 10, 2015 4:16 PM
To: 
Subject: Re: How to set limit on “Acquire New IP” for isolated network

Hi Sonali,

In global settings we have the below option to control the public ips use.
max.project.public.ips  The default maximum number of public IPs that can be 
consumed by a project


Thanks,
Jayapal

On 10-Feb-2015, at 4:11 PM, Sonali Jadhav 
mailto:son...@servercentralen.se>>
 wrote:

Hi,

There is one project, created new isolated network for that project.  I 
observed that user can “Acquire New IP” for isolated network.  How do we set 
limit on how much IP users can acquire ? Because this way, user can consume any 
number of public IPs they want.

Yours sincerely,

Sonali Jadhav | System Administrator
Nordiska Servercentralen
Skype ID: sonali.jadhav.sj
E-mail: 
son...@servercentralen.se

Re: How to set limit on “Acquire New IP” for isolated network

[Jayapal Reddy Uradi]

Hi Sonali,

In global settings we have the below option to control the public ips use.
max.project.public.ips  The default maximum number of public IPs that can be 
consumed by a project


Thanks,
Jayapal

On 10-Feb-2015, at 4:11 PM, Sonali Jadhav 
mailto:son...@servercentralen.se>>
 wrote:

Hi,

There is one project, created new isolated network for that project.  I 
observed that user can “Acquire New IP” for isolated network.  How do we set 
limit on how much IP users can acquire ? Because this way, user can consume any 
number of public IPs they want.

Yours sincerely,

Sonali Jadhav | System Administrator
Nordiska Servercentralen
Skype ID: sonali.jadhav.sj
E-mail: 
son...@servercentralen.se

How to set limit on “Acquire New IP” for isolated network

[Sonali Jadhav]

Hi,

There is one project, created new isolated network for that project.  I 
observed that user can “Acquire New IP” for isolated network.  How do we set 
limit on how much IP users can acquire ? Because this way, user can consume any 
number of public IPs they want.

Yours sincerely,

Sonali Jadhav | System Administrator
Nordiska Servercentralen
Skype ID: sonali.jadhav.sj
E-mail: son...@servercentralen.se

Re: Connection issue with the master

[Salvatore Sciacco]

Also, I'd like to understand why some agent connect just fine
2015-02-10 07:07:02,179 INFO  [utils.nio.NioClient] (Agent-Selector:null)
Connecting to 192.168.11.9:8250
2015-02-10 07:07:07,318 INFO  [utils.nio.NioClient] (Agent-Selector:null)
SSL: Handshake done
2015-02-10 07:07:07,319 INFO  [utils.nio.NioClient] (Agent-Selector:null)
Connected to 192.168.11.9:8250



2015-02-10 10:05 GMT+01:00 Salvatore Sciacco :

> Hi Jayapal,
>
> do you mean the keystore in /etc/cloudstack/management or the ssl setting
> in the config?
>
> I already tried removing the keystore but the same was generated (copied?)
> in place of the existing.
>
> Thank you very much!
>
> S.
>
> 2015-02-10 9:53 GMT+01:00 Jayapal Reddy Uradi <
> jayapalreddy.ur...@citrix.com>:
>
>> Hi,
>>
>> This issue is related to ssl keys.
>> Can you remove the keys and try restarting MS and recreate systemvms.
>>
>> Thanks,
>> Jayapal
>> On 10-Feb-2015, at 1:52 PM, Salvatore Sciacco 
>>  wrote:
>>
>> > Hi,
>> >
>> > I have a few hosts and the systemvm (console proxy) which stopped
>> > connecting to the master with ssl error:
>> >
>> > 2015-02-10 08:43:46,057 INFO  [cloud.agent.Agent] (Agent-Handler-4:null)
>> > Reconnecting...
>> > 2015-02-10 08:43:46,058 INFO  [utils.nio.NioClient]
>> (Agent-Selector:null)
>> > Connecting to 111.11.1.1:8250
>> > 2015-02-10 08:43:56,191 ERROR [utils.nio.NioConnection]
>> > (Agent-Selector:null) Unable to initialize the threads.
>> > java.io.IOException: SSL: Fail to init SSL! java.io.IOException:
>> Connection
>> > closed with -1 on reading size.
>> >at com.cloud.utils.nio.NioClient.init(NioClient.java:87)
>> >at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
>> >at java.lang.Thread.run(Thread.java:745)
>> >
>> >
>> >
>> > anybody can sugggest how I can debug the SSL layer? Cients are able to
>> > connect to the port 8250, but they are disconnected just after the
>> > connection is established.
>> >
>> > Thank you very much
>> >
>> > S.
>>
>>
>

Re: Connection issue with the master

[Salvatore Sciacco]

Hi Jayapal,

do you mean the keystore in /etc/cloudstack/management or the ssl setting
in the config?

I already tried removing the keystore but the same was generated (copied?)
in place of the existing.

Thank you very much!

S.

2015-02-10 9:53 GMT+01:00 Jayapal Reddy Uradi :

> Hi,
>
> This issue is related to ssl keys.
> Can you remove the keys and try restarting MS and recreate systemvms.
>
> Thanks,
> Jayapal
> On 10-Feb-2015, at 1:52 PM, Salvatore Sciacco 
>  wrote:
>
> > Hi,
> >
> > I have a few hosts and the systemvm (console proxy) which stopped
> > connecting to the master with ssl error:
> >
> > 2015-02-10 08:43:46,057 INFO  [cloud.agent.Agent] (Agent-Handler-4:null)
> > Reconnecting...
> > 2015-02-10 08:43:46,058 INFO  [utils.nio.NioClient] (Agent-Selector:null)
> > Connecting to 111.11.1.1:8250
> > 2015-02-10 08:43:56,191 ERROR [utils.nio.NioConnection]
> > (Agent-Selector:null) Unable to initialize the threads.
> > java.io.IOException: SSL: Fail to init SSL! java.io.IOException:
> Connection
> > closed with -1 on reading size.
> >at com.cloud.utils.nio.NioClient.init(NioClient.java:87)
> >at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
> >at java.lang.Thread.run(Thread.java:745)
> >
> >
> >
> > anybody can sugggest how I can debug the SSL layer? Cients are able to
> > connect to the port 8250, but they are disconnected just after the
> > connection is established.
> >
> > Thank you very much
> >
> > S.
>
>

Re: Connection issue with the master

[Jayapal Reddy Uradi]

Hi,

This issue is related to ssl keys.
Can you remove the keys and try restarting MS and recreate systemvms.

Thanks,
Jayapal
On 10-Feb-2015, at 1:52 PM, Salvatore Sciacco 
 wrote:

> Hi,
> 
> I have a few hosts and the systemvm (console proxy) which stopped
> connecting to the master with ssl error:
> 
> 2015-02-10 08:43:46,057 INFO  [cloud.agent.Agent] (Agent-Handler-4:null)
> Reconnecting...
> 2015-02-10 08:43:46,058 INFO  [utils.nio.NioClient] (Agent-Selector:null)
> Connecting to 111.11.1.1:8250
> 2015-02-10 08:43:56,191 ERROR [utils.nio.NioConnection]
> (Agent-Selector:null) Unable to initialize the threads.
> java.io.IOException: SSL: Fail to init SSL! java.io.IOException: Connection
> closed with -1 on reading size.
>at com.cloud.utils.nio.NioClient.init(NioClient.java:87)
>at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
>at java.lang.Thread.run(Thread.java:745)
> 
> 
> 
> anybody can sugggest how I can debug the SSL layer? Cients are able to
> connect to the port 8250, but they are disconnected just after the
> connection is established.
> 
> Thank you very much
> 
> S.

Connection issue with the master

[Salvatore Sciacco]

Hi,

I have a few hosts and the systemvm (console proxy) which stopped
connecting to the master with ssl error:

2015-02-10 08:43:46,057 INFO  [cloud.agent.Agent] (Agent-Handler-4:null)
Reconnecting...
2015-02-10 08:43:46,058 INFO  [utils.nio.NioClient] (Agent-Selector:null)
Connecting to 111.11.1.1:8250
2015-02-10 08:43:56,191 ERROR [utils.nio.NioConnection]
(Agent-Selector:null) Unable to initialize the threads.
java.io.IOException: SSL: Fail to init SSL! java.io.IOException: Connection
closed with -1 on reading size.
at com.cloud.utils.nio.NioClient.init(NioClient.java:87)
at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
at java.lang.Thread.run(Thread.java:745)



anybody can sugggest how I can debug the SSL layer? Cients are able to
connect to the port 8250, but they are disconnected just after the
connection is established.

Thank you very much

S.