Re: Cloudstack deployment

[Pierre-Luc Dion]

Got this type of issue with previous Cloudstack version, turn out that the
LABEL of Networks in Cloudstack did not match those define in XenServer.
Could it be the problem here ?

Also, if you applied xenserver hotfixes after adding xenserver to your
cloudstack, the hotfix might have replace some script on the xenserver ,
refer to:
https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.1
3.2. Upgrade from 3.0.x to 4.2.0   18-G



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Feb 4, 2014 at 2:21 PM, Victor Rodionov wrote:

> Hi, vhd-util already installed. I try this template, but it sill not
> working.
>
>
> 2014-02-03 Mike Tutkowski :
>
> > Additionally you should probably be using this system template:
> >
> >
> >
> http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
> >
> >
> > On Mon, Feb 3, 2014 at 6:54 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com
> > > wrote:
> >
> > > Check out section 4.5.3.3:
> > >
> > >
> > >
> >
> https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html#management-server-install
> > >
> > >
> > > On Mon, Feb 3, 2014 at 6:52 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com> wrote:
> > >
> > >> You are likely missing vhd-util. It needs to be downloaded and place
> in
> > >> /opt/cloud/bin.
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the cloud<
> > http://solidfire.com/solution/overview/?video=play>
> > > *(tm)*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
> >
>

unable to remove xenserver host from a cluster properly

[Pierre-Luc Dion]

"com.cloud.agent.api.PoolEjectCommand":{"hostuuid":"571299d2-e0c8-4cc4-a730-8d9aaf9f0f81","wait":0}}]
}
2014-02-04 15:04:49,400 DEBUG [agent.transport.Request]
(catalina-exec-22:null) Seq 5-882053032: Executing:  { Cmd , MgmtId:
6794168500400, via: 5, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.PoolEjectCommand":{"hostuuid":"571299d2-e0c8-4cc4-a730-8d9aaf9f0f81","wait":0}}]
}
2014-02-04 15:04:49,400 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-448:null) Seq 5-882053032: Executing request
2014-02-04 15:04:49,416 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-225:null) Add master connection through 172.16.20.34 for
pool(null)
2014-02-04 15:04:49,609 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-363:null) Ping from 5
2014-02-04 15:04:49,648 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-300:null) Ping from 4
2014-02-04 15:04:49,649 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-358:null) Ping from 1
2014-02-04 15:04:49,665 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-31:null) Seq 4-557056006: Response Received:
2014-02-04 15:04:49,666 DEBUG [agent.transport.Request]
(DirectAgent-31:null) Seq 4-557056006: Processing:  { Ans: , MgmtId:
6794168500400, via: 4, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}] }
2014-02-04 15:04:49,666 DEBUG [agent.manager.AgentAttache]
(DirectAgent-31:null) Seq 4-557056006: Unable to find listener.
2014-02-04 15:04:49,678 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-477:null) Seq 1-1530855430: Response Received:
2014-02-04 15:04:49,678 DEBUG [agent.transport.Request]
(DirectAgent-477:null) Seq 1-1530855430: Processing:  { Ans: , MgmtId:
6794168500400, via: 1, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}] }
2014-02-04 15:04:49,684 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-382:null) Seq 5-882049030: Response Received:
2014-02-04 15:04:49,684 DEBUG [agent.transport.Request]
(DirectAgent-382:null) Seq 5-882049030: Processing:  { Ans: , MgmtId:
6794168500400, via: 5, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
}
2014-02-04 15:04:49,770 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-448:null) New master for the XenPool is
571299d2-e0c8-4cc4-a730-8d9aaf9f0f81 : 172.16.20.37
2014-02-04 15:04:49,773 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-448:null) Designating the new master to 172.16.20.37
2014-02-04 15:04:49,773 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-448:null) Designating the new master to 172.16.20.37
2014-02-04 15:04:49,859 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-225:null) Vm cpu utilization 0.005
2014-02-04 15:04:49,996 WARN  [xen.resource.CitrixResourceBase]
(DirectAgent-225:null) Error while collecting disk stats from :
You gave an invalid object reference.  The object may have recently been
deleted.  The class parameter gives the type of reference given, and the
handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:209)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBDMetrics.getIoReadKbs(VBDMetrics.java:210)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getVmStats(CitrixResourceBase.java:2791)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2691)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)




Thanks,



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Cloudstack documentation

[Pierre-Luc Dion]

Hi all,

I would like to know where we can get newer version of documentation for
Cloudstack. Look like the documentation site is not updated since 4.2.0. I
know that the documentation system will change, is their any information
about it somewhere?

Also, I would like to contribute as well.

Thanks,

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: Cloudstack documentation

[Pierre-Luc Dion]

Thanks Wido,

Cool, look like the rtd version is in there too.  so I guest we need a lot
of work on conversion from publican to RST?




Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander  wrote:

> On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
>
>> Hi all,
>>
>> I would like to know where we can get newer version of documentation for
>> Cloudstack. Look like the documentation site is not updated since 4.2.0. I
>> know that the documentation system will change, is their any information
>> about it somewhere?
>>
>>
> Yes, it moved to it's own repository: https://git-wip-us.apache.org/
> repos/asf?p=cloudstack-docs.git
>
> $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
>
> From there you can probably build the docs yourself. Be aware that we are
> moving to RST.
>
>
>  Also, I would like to contribute as well.
>>
>>
> Patches are always welcome!
>
>  Thanks,
>>
>> Pierre-Luc Dion
>> Architecte de Solution Cloud | Cloud Solutions Architect
>> - - -
>>
>> *CloudOps*420 rue Guy
>>
>> Montréal QC  H3J 1S6
>> www.cloudops.com
>> @CloudOps_
>>
>>
>

Re: Cloudstack documentation

[Pierre-Luc Dion]

Thanks Sebastien,


Seams quite complete! Is there a reason why doc url on
http://cloudstack.apache.org/ still point to the old doc ?



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Mar 18, 2014 at 10:16 AM, sebgoa  wrote:

>
> On Mar 18, 2014, at 3:02 PM, Pierre-Luc Dion  wrote:
>
> > Thanks Wido,
> >
> > Cool, look like the rtd version is in there too.  so I guest we need a
> lot
> > of work on conversion from publican to RST?
>
> It' already done :) I'd be mean I would tell you to search the mailing
> list :)
>
> If you search the cloudstack mirrors on github:
> https://github.com/orgs/apache?query=cloudstack
>
> you will see four documentation repo.
> cloudstack-docs
> cloudstack-docs-rn (release notes)
> cloudstack-docs-admin (the admin guide)
> cloudstack-docs-install (the installation guide)
>
> the rn, admin and installation guide are pure rest, and are a conversion
> of the publican to .rst. there is still work to do, especially on the admin
> guide.
>
> These docs are pushed automatically to readthedocs.org and provide:
>
> http://apache-cloudstack-release-notes.readthedocs.org/en/latest/
> http://cloudstack-installation.readthedocs.org/en/latest/
> http://cloudstack-administration.readthedocs.org/en/latest/
> http://docs.cloudstack.apache.org
>
> I am actively working on cleaning this up and fixing the URLs/CNAMEs.
>
> The easiest way to contribute is *really* to visit the RTD sites and click
> on the "edit on github" button, this will automatically fork the repo in
> your github account.
> You can then submit a pull request. It will send a notification on dev@list 
> and we can merge it.
>
> There is still lots of work to do, both on the formatting (the conversion
> was not perfect) and the content of course.
>
> Have at it, I'd be delighted to merge your patches :)
>
> -sebastien
>
> >
> >
> >
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 514-447-3456, 1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
> > On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander 
> wrote:
> >
> >> On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
> >>
> >>> Hi all,
> >>>
> >>> I would like to know where we can get newer version of documentation
> for
> >>> Cloudstack. Look like the documentation site is not updated since
> 4.2.0. I
> >>> know that the documentation system will change, is their any
> information
> >>> about it somewhere?
> >>>
> >>>
> >> Yes, it moved to it's own repository: https://git-wip-us.apache.org/
> >> repos/asf?p=cloudstack-docs.git
> >>
> >> $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
> >>
> >> From there you can probably build the docs yourself. Be aware that we
> are
> >> moving to RST.
> >>
> >>
> >> Also, I would like to contribute as well.
> >>>
> >>>
> >> Patches are always welcome!
> >>
> >> Thanks,
> >>>
> >>> Pierre-Luc Dion
> >>> Architecte de Solution Cloud | Cloud Solutions Architect
> >>> - - -
> >>>
> >>> *CloudOps*420 rue Guy
> >>>
> >>> Montréal QC  H3J 1S6
> >>> www.cloudops.com
> >>> @CloudOps_
> >>>
> >>>
> >>
>
>

Re: Cloudstack documentation

[Pierre-Luc Dion]

Thanks Sebastien for the pull request.
I will submit a new one to fix a tables and internal reference links later
this week.

I haven't found how we should update internal links. Look like we would
have to change them for ex:  `networking2.html#create vpn`
Anyone know another method to create link to topic from another file?

Also, could we split networking2.rst file into multiple parts?

Thanks

Le mardi 18 mars 2014, sebgoa  a écrit :

>
> On Mar 18, 2014, at 3:50 PM, Pierre-Luc Dion 
> >
> wrote:
>
> > Thanks Sebastien,
> >
> >
> > Seams quite complete! Is there a reason why doc url on
> > http://cloudstack.apache.org/ still point to the old doc ?
>
> My plan is to make the switch once 4.3 is out.
>
> There is still some cleaning up to do on the .rst/RTD stuff which would be
> nice to fix before making it official.
>
> Also, we might have to vote on docs releases...haven't touched that one yet
> :)
>
> -sebastien
>
> >
> >
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 514-447-3456, 1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
> > On Tue, Mar 18, 2014 at 10:16 AM, sebgoa >
> wrote:
> >
> >>
> >> On Mar 18, 2014, at 3:02 PM, Pierre-Luc Dion 
> >> >
> wrote:
> >>
> >>> Thanks Wido,
> >>>
> >>> Cool, look like the rtd version is in there too.  so I guest we need a
> >> lot
> >>> of work on conversion from publican to RST?
> >>
> >> It' already done :) I'd be mean I would tell you to search the mailing
> >> list :)
> >>
> >> If you search the cloudstack mirrors on github:
> >> https://github.com/orgs/apache?query=cloudstack
> >>
> >> you will see four documentation repo.
> >> cloudstack-docs
> >> cloudstack-docs-rn (release notes)
> >> cloudstack-docs-admin (the admin guide)
> >> cloudstack-docs-install (the installation guide)
> >>
> >> the rn, admin and installation guide are pure rest, and are a conversion
> >> of the publican to .rst. there is still work to do, especially on the
> admin
> >> guide.
> >>
> >> These docs are pushed automatically to readthedocs.org and provide:
> >>
> >> http://apache-cloudstack-release-notes.readthedocs.org/en/latest/
> >> http://cloudstack-installation.readthedocs.org/en/latest/
> >> http://cloudstack-administration.readthedocs.org/en/latest/
> >> http://docs.cloudstack.apache.org
> >>
> >> I am actively working on cleaning this up and fixing the URLs/CNAMEs.
> >>
> >> The easiest way to contribute is *really* to visit the RTD sites and
> click
> >> on the "edit on github" button, this will automatically fork the repo in
> >> your github account.
> >> You can then submit a pull request. It will send a notification on
> dev@list and we can merge it.
> >>
> >> There is still lots of work to do, both on the formatting (the
> conversion
> >> was not perfect) and the content of course.
> >>
> >> Have at it, I'd be delighted to merge your patches :)
> >>
> >> -sebastien
> >>
> >>>
> >>>
> >>>
> >>>
> >>> Pierre-Luc Dion
> >>> Architecte de Solution Cloud | Cloud Solutions Architect
> >>> 514-447-3456, 1101
> >>> - - -
> >>>
> >>> *CloudOps*420 rue Guy
> >>> Montréal QC  H3J 1S6
> >>> www.cloudops.com
> >>> @CloudOps_
> >>>
> >>>
> >>> On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander 
> >>> 
> >
> >> wrote:
> >>>
> >>>> On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
> >>>>
> >>>>> Hi all,
> >>>>>
> >>>>> I would like to know where we can get newer version of documentation
> >> for
> >>>>> Cloudstack. Look like the documentation site is not updated since
> >> 4.2.0. I
> >>>>> know that the documentation system will change, is their any
> >> information
> >>>>> about it somewhere?
> >>>>>
> >>>>>
> >>>> Yes, it moved to it's own repository: https://git-wip-us.apache.org/
> >>>> repos/asf?p=cloudstack-docs.git
> >>>>
> >>>> $ git clone
> https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
> >>>>
> >>>> From there you can probably build the docs yourself. Be aware that we
> >> are
> >>>> moving to RST.
> >>>>
> >>>>
> >>>> Also, I would like to contribute as well.
> >>>>>
> >>>>>
> >>>> Patches are always welcome!
> >>>>
> >>>> Thanks,
> >>>>>
> >>>>> Pierre-Luc Dion
> >>>>> Architecte de Solution Cloud | Cloud Solutions Architect
> >>>>> - - -
> >>>>>
> >>>>> *CloudOps*420 rue Guy
> >>>>>
> >>>>> Montréal QC  H3J 1S6
> >>>>> www.cloudops.com
> >>>>> @CloudOps_
> >>>>>
> >>>>>
> >>>>
> >>
> >>
>
>

-- 

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: [DOCS] Re: docs question

[Pierre-Luc Dion]

I like this workflow.  I'm not experienced with pull request, hope it's not
be complicated for a doc repo...

Stagging site seams perfect !


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Mar 20, 2014 at 10:17 AM, sebgoa  wrote:

> Mainly informing myself for archiving purposes :)
>
> We stand at:
>
> http://docs.cloudstack.apache.org
> http://docs.cloudstack.apache.org/projects/cloudstack-installation
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes
> http://docs.cloudstack.apache.org/projects/cloudstack-administration
>
> That's the cleanest I can make it without creating new CNAMEs or changing
> our repo architecture.
>
> I used those URLs in the new Documentation drop down menu on the site, it
> looks like this in staging:
>
> http://cloudstack.staging.apache.org
>
> and as I am typing this, I realized that I actually published the site so
> it's live, oupsYell if you see a problem
>
> I kept a link to the old docs called "Obsolete Docs"
>
> PS:
> Thanks, to Pierre Luc, Nux, Geoff and Chris snow who sent pr testing the
> new workflow.
> Thanks to Shankar, Paul, Ian and Tuna for new content already.
>
>
> On Mar 19, 2014, at 1:48 PM, sebgoa  wrote:
>
> >
> > On Mar 19, 2014, at 12:09 PM, sebgoa  wrote:
> >
> >> Hi,
> >>
> >> Question #1:
> >> --
> >>
> >> With the new move to RTD we need to agree on a URL naming convention.
> >>
> >> Currently we have one CNAME that points to RTD site (don't worry about
> the content on that page):
> >>
> >> http://docs.cloudstack.apache.org
> >>
> >> Using RTD sub projects features this gives us the following URLs to get
> to the admin and install guide.
> >>
> >> http://docs.cloudstack.apache.org/projects/cloudstack-installation
> >> http://docs.cloudstack.apache.org/projects/cloudstack-administration
> >>
> >> The cloudstack-installation and cloudstack-administration are not
> changeable, RTD does not allow to change that.
> >>
> >> Are we fine with this ? It seems a bit long to me.
> >>
> >> If we are not fine with this, the alternative is to create other CNAMEs
> via apache infra to point to those guides.
> >>
> >> Question #2:
> >> --
> >>
> >> What do we want the landing page http://docs.cloudstack.apache.org to
> have ?
> >>
> >> On the cloudstack.apache.org website I was thinking of extending the
> tab to link to each guide. This would work well with a CNAME per guide.
> >> But if we keep a single link to 'DOCS' on our main website, then the
> question of the docs landing page is there.
> >>
> >>
> >> what say you folks ?
> >>
> >
> > To illustrate a bit, check:
> >
> > http://cloudstack.staging.apache.org
> >
> > Then click on the 'documentation' drop downselect 'Doc Root' or
> 'Installation Docs' or 'Release Notes'
> >
> >>
> >> -Sebastien
> >
>
>

Re: [GitHub] cloudstack-docs-admin pull request: fixed internal links, tables, ...

[Pierre-Luc Dion]

I've update pretty much all internal links in the admin guide, although I
haven't found following sections:
- section #2 Cloud Infrastructure concept is missing ?
- appendixes

Should I copy the old appendix in the admin guide ?

Thanks,


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Mar 20, 2014 at 9:43 PM, pdion891  wrote:

> GitHub user pdion891 opened a pull request:
>
> https://github.com/apache/cloudstack-docs-admin/pull/3
>
> fixed internal links, tables, CLOUDSTACK-5954
>
> Fixed internal links, forgotten tables and  update-ssl.png file :
> CLOUDSTACK-5954
> add default OS in .gitignore file.
>
> ```
> $ sphinx-build -b html source build
> Running Sphinx v1.2.2
> loading pickled environment... done
> building [html]: targets for 19 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> preparing documents... done
> writing output... [100%] virtual_machines
> writing additional files... genindex search
> copying images... [100%] _static/images/egress-firewall-rule.png
> copying static files... done
> copying extra files... done
> dumping search index... done
> dumping object inventory... done
> build succeeded.
> ```
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/cloudops/cloudstack-docs-admin master
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/cloudstack-docs-admin/pull/3.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #3
>
> 
> commit 6b2c8268f67328eaf2088166631dcd4d059521b0
> Author: Pierre-Luc Dion 
> Date:   2014-03-20T01:29:33Z
>
> fixed images links, tables, toctree
>
> commit 08e60ee04b10be2437bfd701e002787ab8dafe97
> Author: Pierre-Luc Dion 
> Date:   2014-03-21T01:30:33Z
>
> fixed internal links, tables, CLOUDSTACK-5954
>
> commit 0647b9740a15faf51cbb81894927271b611023bf
> Author: Pierre-Luc Dion 
> Date:   2014-03-21T01:41:26Z
>
> replaced â EURO\" by :
>
> 
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

build cloudstack 4.3 from source

[Pierre-Luc Dion]

Hi,

I'm trying to build Cloudstack 4.3 from the 4.3 branch with nodist package.

Do I need to place the mysql-connector-java-5.1.29-bin.jar somewhere?

here is the build output log:

[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/var/lib/jenkins/workspace/CloudStack4.3_nodist_rpms/dist/rpmbuild/BUILD/cloudstack-4.3.0/framework/db/src/com/cloud/utils/db/StaticStrategy.java:[26,21]
error: package com.mysql.jdbc does not exist



is there any reference about this in the doc or the wiki ? I've found
nothing so far.

Thanks


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: [GitHub] cloudstack-docs-admin pull request: Co pullr2

[Pierre-Luc Dion]

Look like the merge damaged the documentation :-(

Fixing it now...



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Mon, Mar 24, 2014 at 6:46 PM, asfgit  wrote:

> Github user asfgit closed the pull request at:
>
> https://github.com/apache/cloudstack-docs-admin/pull/5
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

docs-install: hyper-V installation

[Pierre-Luc Dion]

I was reviewing doc formating last night and I can't figure out this
section:

http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/hypervisor_installation.html#preparation-checklist-for-hyper-v

it seams to be a table  but I can't figure out what go where.

Should I fill out a bug for this ? of if someone can show me what it should
look like I will fix it.

Thanks.

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: build cloudstack 4.3 from source

[Pierre-Luc Dion]

Hi all,

Any chance someone would know where we should place the MySQL connector.jar
file in order to build with nodist?
I haven't found any instruction so far.

Regards,



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Mon, Mar 24, 2014 at 4:53 PM, Pierre-Luc Dion  wrote:

> Hi,
>
> I'm trying to build Cloudstack 4.3 from the 4.3 branch with nodist
> package.
>
> Do I need to place the mysql-connector-java-5.1.29-bin.jar somewhere?
>
> here is the build output log:
>
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] 
> /var/lib/jenkins/workspace/CloudStack4.3_nodist_rpms/dist/rpmbuild/BUILD/cloudstack-4.3.0/framework/db/src/com/cloud/utils/db/StaticStrategy.java:[26,21]
>  error: package com.mysql.jdbc does not exist
>
>
>
> is there any reference about this in the doc or the wiki ? I've found
> nothing so far.
>
> Thanks
>
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
>
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>

Re: Unable to deploy systemvms

[Pierre-Luc Dion]

Tejas,

Did you add the network label names in Cloudstack ?  You need to specify
the network label name in Cloudstack that are configured in XenServer. I'm
suspecting that the current issue is that CloudStack cannot map the Storage
Network from is config in XenServer so xenserver cannot reach the secondary
storage.

I've add an attachment on where to look at in Cloudstack. If you have
access to XenCenter you have to use name of networks under networking tab
on the XenServer host.

you can refer to:
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/hypervisor_installation.html#citrix-xenserver-installation-for-cloudstack

Regards,




Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Wed, Apr 2, 2014 at 8:54 AM, Tejas Gadaria  wrote:

> Hi Yitao,
>
> xenbr0 : acting as Management network and no VLAN is assigned to it
> xenbr1 : acting as public, guest storage network. All of this are in same
> VLAN.
> Also I have given same "name-label" as here in Cloudstack network
> configuraion.
>
> I don't know much about xen VLAN networking..if anything wrong please
> point it out.
>
> [root@xen-dev ~]# xe network-list
> uuid ( RO): bfb89346-9eae-4554-a46a-59f9b4587983
>   name-label ( RW): cloud_link_local_network
> name-description ( RW): link local network used by system vms
>   bridge ( RO): xapi0
>
>
> uuid ( RO): eeb9fb94-7468-6b78-aaae-8d4e84b48afd
>   name-label ( RW): Host internal management network
> name-description ( RW): Network on which guests will be assigned a
> private link-local IP address which can be used to talk XenAPI
>   bridge ( RO): xenapi
>
>
> uuid ( RO): 90f6f78a-d4d8-463a-ccca-e28f7ea4e7d2
>   name-label ( RW): cloud-manage
> name-description ( RW):
>   bridge ( RO): xenbr0
>
>
> uuid ( RO): 88f0843e-feb9-44d0-5a04-06f32a258b81
>   name-label ( RW): cloud-public
> name-description ( RW):
>   bridge ( RO): xenbr1
>
>
> Regards,
> Tejas
>
>
>
> On Wed, Apr 2, 2014 at 5:42 PM, Yitao Jiang  wrote:
>
> > Can you post your network configuration here, and do u able make
> operation
> > on xenseever through xencenter? May be something wrong with ur storage
> > On Apr 2, 2014 6:47 PM, "Tejas Gadaria"  wrote:
> >
> > > Hi Punith,
> > >
> > > Thanks for reply,
> > >
> > > I have already uploaded
> systemvm64template-2014-01-14-master-xen.vhd.bz2
> > in
> > > secondary .
> > >
> > > [root@con-xen ~]# ls -lR /vol/
> > > /vol/:
> > > total 8
> > > drwxr-xr-x 2 root root 4096 Apr  2 12:46 primary
> > > drwxr-xr-x 3 root root 4096 Apr  2 12:14 secondary
> > >
> > > /vol/primary:
> > > total 4
> > > -rw-r--r-- 1 root root 11 Apr  2 16:03
> > > hb-ecff5b59-a2bc-4c0c-9ec8-05f7b4cda546
> > >
> > > /vol/secondary:
> > > total 4
> > > drwxr-xr-x 3 root root 4096 Apr  2 12:14 template
> > >
> > > /vol/secondary/template:
> > > total 4
> > > drwxr-xr-x 3 root root 4096 Apr  2 12:14 tmpl
> > >
> > > /vol/secondary/template/tmpl:
> > > total 4
> > > drwxr-xr-x 3 root root 4096 Apr  2 12:14 1
> > >
> > > /vol/secondary/template/tmpl/1:
> > > total 4
> > > drwxr-xr-x 2 root root 4096 Apr  2 12:26 1
> > >
> > > /vol/secondary/template/tmpl/1/1:
> > > total 2565016
> > > -rw-r--r-- 1 root root 2626564608 Apr  2 12:19
> > > 041bb2b7-2c84-4a72-a2bb-573d6c1ba56e.vhd
> > > -rw-r--r-- 1 root root287 Apr  2 12:26 template.properties
> > >
> > >
> > > Regards,
> > > Tejas
> > >
> > >
> > > On Wed, Apr 2, 2014 at 3:59 PM, Punith S 
> wrote:
> > >
> > > > hi,
> > > >
> > > > check whether you have seeded the vdh util for sysytem vms in
> secondary
> > > > storage.
> > > >
> > > >
> > >
> >
> http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/installation.html#prepare-the-system-vm-template
> > > >
> > > > thanks.
> > > >
> > > >
> > > > On Wed, Apr 2, 2014 at 3:54 PM, Tejas Gadaria  >
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > >

RTD documentations

[Pierre-Luc Dion]

Hi,

I was reviewing how to use RTD for CloudStack documentation and look like
we could use git branches to match product and doc version. This way we
could provide documentation update while and keep the documentation match
the product version. it should also be possible to define the default
("latest") to a specific branch so we could have  branches for  4.3, 4.4
and still have the default documentation pointing to 4.3 as the latest.

Did any one tested that?

RTD support also Tags for documentation versioning but if we want to keep
matching doc version and CS version we couldn't perform fixes in the doc
without updating the doc version.


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: Unable to deploy systemvms

[Pierre-Luc Dion]

Tejas,

The SSVM will mount the NFS share using is Storage network interface if
define otherwise it will mount it using is management NIC.  To download the
template, the traffic from the SSVM will go from is Public interface. You
should be able to ping the SSVM public IP, the current setup might have a
networking issue such as an improper VLAN ID defined or label.



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Apr 3, 2014 at 2:31 AM, Tejas Gadaria  wrote:

> Hi Dion,
>
> Thanks for the clue,I was missing 'cloud traffic label' there.
> One step ahead Now SSVM and CPVM is UP & running.  I am able to ping both
> private ip but not Public ip from Management server and link local is also
> pinging from hypervisor . I tried SSVM health check. every thing fine.
> secstorage.allowed.internal.sites = Management server ip.
>
> 2014-04-03 11:15:55,280 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-5: Processing Seq 2-5:  { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 11,
>
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2014-04-03 11:15:55,288 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-5: Sending Seq 2-5:  { Ans: , MgmtId:
> 345049296663, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-04-03 11:15:55,996 DEBUG [o.a.c.s.RemoteHostEndPoint]
> (Timer-11:ctx-67fcb05a) Sending command
> org.apache.cloudstack.storage.command.DownloadProgressCommand to host: 3
> 2014-04-03 11:15:55,998 DEBUG [c.c.a.t.Request] (Timer-11:ctx-67fcb05a) Seq
> 3-140181514: Sending  { Cmd , MgmtId: 345049296663, via: 3(s-1-VM), Ver:
> v1, Flags: 100011,
>
> [{"org.apache.cloudstack.storage.command.DownloadProgressCommand":{"jobId":"c9ad6108-ddcd-44a1-8e62-9d7ab76e4834","request":"GET_STATUS","hvm":false,"description":"CentOS
> 5.6(64-bit) no GUI
>
> (XenServer)","checksum":"905cec879afd9c9d22ecc8036131a180","maxDownloadSizeInBytes":53687091200,"id":5,"resourceType":"TEMPLATE","installPath":"template/tmpl/1/5","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://
> 10.129.151.60/vol/secondary","_role":"Image"}},"url":"
> http://download.cloud.com/templates/builtin/centos56-x86_64.vhd.bz2
>
> ","format":"VHD","accountId":1,"name":"centos56-x86_64-xen","secUrl":"nfs://
> 10.129.151.60/vol/secondary","wait":0}}] }
> 2014-04-03 11:15:55,999 DEBUG [o.a.c.s.RemoteHostEndPoint]
> (Timer-10:ctx-7539f2bf) Sending command
> org.apache.cloudstack.storage.command.DownloadProgressCommand to host: 3
> 2014-04-03 11:15:56,001 DEBUG [c.c.a.t.Request] (Timer-10:ctx-7539f2bf) Seq
> 3-140181515: Sending  { Cmd , MgmtId: 345049296663, via: 3(s-1-VM), Ver:
> v1, Flags: 100011,
>
> [{"org.apache.cloudstack.storage.command.DownloadProgressCommand":{"jobId":"8c3263f0-b796-4f28-a965-6f2ef421f815","request":"GET_STATUS","hvm":false,"description":"CentOS
> 5.3(64-bit) no GUI
>
> (XenServer)","checksum":"b63d854a9560c013142567bbae8d98cf","maxDownloadSizeInBytes":53687091200,"id":2,"resourceType":"TEMPLATE","installPath":"template/tmpl/1/2","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://
> 10.129.151.60/vol/secondary","_role":"Image"}},"url":"
>
> http://download.cloud.com/templates/builtin/f59f18fb-ae94-4f97-afd2-f84755767aca.vhd.bz2
> ","format":"VHD","accountId":1,"name":"centos53-x86_64","secUrl":"nfs://
> 10.129.151.60/vol/secondary","wait":0}}] }
> 2014-04-03 11:15:56,021 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-9:null) Seq 3-140181515: Processing:  { Ans: ,
> MgmtId: 345049296663, via: 3, Ver: v1, Flags: 10,
>
> [{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"8c3263f0-b796-4f28-a965-6f2ef421f815","*downloadPct":0,"errorString":"No
> route to
>
> host","downloadStatus":"DOWNLOAD_ERROR","downloadPath":"/mnt/SecStorage/083f43be-

release note documentation

[Pierre-Luc Dion]

At the hackathon of CCCNA14 with Sebastien, we made few tests the RTD for
documentation versioning.

Look like we can use branch instead of tag for versioning and we can also
select which branches are published on RTD.org

So, in order to have doc version match product version, would it make sense
to create a branch call 4.3.0 for the current CS version and start updating
master for next version 4.4 ? once we will have 4.4 pretty much ready we
will be able to create new branch 4.4.

By using branches it allow us to update documentation without having to
update is version.

Make sense?  Have we missing a potential GIT behaviour  doing it this way?


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: Secondary Storage limits

[Pierre-Luc Dion]

Does the templates really use 10GB? because if you create a template from
an Instance that have 10GB disk offering, the template might only consume
2GB on the secondary storage which is the used space of the virtual disk.


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Apr 17, 2014 at 9:38 AM, Gaurav Aradhye
wrote:

> Hi,
>
> I came across this scenario where secondary storage limit of the domain
> gets exceeded.
>
> Suppose we have set secondary storage limit for a domain as 20 GB and we
> register 2 templates of 10 GB each in the domain. Now as already the limit
> is reached, new template won't be registered.
>
> But suppose we register 2 templates of 9 GB each, then 2 GBs are left
> available. But now if I register and download a template of 10 GB, then
> still it will be successful although it exceeds the limit.
>
> This might be happening because it won't know the size of the template
> while registering it. But at least then the download operation should fail.
>
> Is this correct behaviour? If not, I will log a bug for this.
>
> Regards,
> Gaurav
>

Re: Secondary Storage limits

[Pierre-Luc Dion]

Does "storage.overprovisioning.factor" Global setting is set to 1?


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Apr 17, 2014 at 9:57 AM, Gaurav Aradhye
wrote:

> I used those numbers just for example. Here I am not creating template from
> Snapshot, I am registering through URL and then downloading it. Even in 2
> GB case, it will exceed the limit if I set the limit as 5 GB. Here I am
> able to register 3 templates and get the total count as 6 GB which exceeds
> the limit.
>
> Regards,
> Gaurav
>
>
> On Thu, Apr 17, 2014 at 7:20 PM, Pierre-Luc Dion 
> wrote:
>
> > Does the templates really use 10GB? because if you create a template from
> > an Instance that have 10GB disk offering, the template might only consume
> > 2GB on the secondary storage which is the used space of the virtual disk.
> >
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 855-OK-CLOUD (855-652-5683) x1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
> > On Thu, Apr 17, 2014 at 9:38 AM, Gaurav Aradhye
> > wrote:
> >
> > > Hi,
> > >
> > > I came across this scenario where secondary storage limit of the domain
> > > gets exceeded.
> > >
> > > Suppose we have set secondary storage limit for a domain as 20 GB and
> we
> > > register 2 templates of 10 GB each in the domain. Now as already the
> > limit
> > > is reached, new template won't be registered.
> > >
> > > But suppose we register 2 templates of 9 GB each, then 2 GBs are left
> > > available. But now if I register and download a template of 10 GB, then
> > > still it will be successful although it exceeds the limit.
> > >
> > > This might be happening because it won't know the size of the template
> > > while registering it. But at least then the download operation should
> > fail.
> > >
> > > Is this correct behaviour? If not, I will log a bug for this.
> > >
> > > Regards,
> > > Gaurav
> > >
> >
>

Re: release note documentation

[Pierre-Luc Dion]

Should we have a page on wiki explaining how we would handle release-notes
on RTD ? and then vote on the method?
I'm not seeing other alternative to branches exept having one RTD project
for each release-notes.





Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Apr 15, 2014 at 12:28 PM, David Nalley  wrote:

> So I think it makes sense for most documents to point to feature
> version (e.g. 4.3 branch, 4.4 branch.) E.g. docs for 4.3.1 should be
> materially the same as 4.3.0 from a docs standpoint. Release notes are
> the exception here, though perhaps they could be dealt with in an
> additive way.
>
> --David
>
> On Tue, Apr 15, 2014 at 11:17 AM, sebgoa  wrote:
> > To add to what Pierre-Luc said:
> >
> > Readthedocs has something they call "releases" but those are in fact
> builds that point to a branch. Not a specific tag.
> >
> > So the release version of the doc we would see on the website will be
> the live state of the release branch, not a tag that we could vote on.
> >
> > That said, we have not yet discussed whether or not we need to formally
> vote on doc releases :)
> >
> > -sebastien
> >
> >
> > On Apr 15, 2014, at 3:56 PM, Daan Hoogland 
> wrote:
> >
> >> makes sense! the only behavior that needs to be taken into account is
> >> that of any publication scripts that we might write. So it seems to me
> >> this is the best result we have from this version of the hackathon :(
> >> & :)
> >>
> >> On Tue, Apr 15, 2014 at 2:54 PM, Pierre-Luc Dion 
> wrote:
> >>> At the hackathon of CCCNA14 with Sebastien, we made few tests the RTD
> for
> >>> documentation versioning.
> >>>
> >>> Look like we can use branch instead of tag for versioning and we can
> also
> >>> select which branches are published on RTD.org
> >>>
> >>> So, in order to have doc version match product version, would it make
> sense
> >>> to create a branch call 4.3.0 for the current CS version and start
> updating
> >>> master for next version 4.4 ? once we will have 4.4 pretty much ready
> we
> >>> will be able to create new branch 4.4.
> >>>
> >>> By using branches it allow us to update documentation without having to
> >>> update is version.
> >>>
> >>> Make sense?  Have we missing a potential GIT behaviour  doing it this
> way?
> >>>
> >>>
> >>> Pierre-Luc Dion
> >>> Architecte de Solution Cloud | Cloud Solutions Architect
> >>> 855-OK-CLOUD (855-652-5683) x1101
> >>> - - -
> >>>
> >>> *CloudOps*420 rue Guy
> >>> Montréal QC  H3J 1S6
> >>> www.cloudops.com
> >>> @CloudOps_
> >>
> >>
> >>
> >> --
> >> Daan
> >
>

Re: release note documentation

[Pierre-Luc Dion]

at this point do we have to create a new [discuss] thread?  I'm still not
familiar with Apache process so I can start a new thread.

I would also add few consideration.
by using branches, let say we create a branch 4.3 for current CS version,
this branch would be the default visible on RTD and we wouldn't see latest
anymore, the master branch would be the work in progress for version 4.4 of
CS. although, if we have a need for 4.3.1, then we would have to create a
branch 4.3.1 and update doc so it reflect new fixes, instructions,
master and 4.3.1 branch would not be visible on RTD until the CS version is
released, but branches would be available on the GIT repo.

This way,  we can work on the release-note documentation as the CS version
is under development, this RN is not visible from RTD because the CS
version is not released but it is available in the gitrepo as master branch
or sub version branch.  So on RTD we would only see  RN of Released version
of CloudStack.

if typo or upgrade notes have to be corrected on RN of release CloudStack
Version, those fix would have to be performed on the branch directly and
the branch would have to be rebuild in RTD, this would not change the
documentation version show on RTD.

I guest this working method need a vote? at lease a [discuss] ? but if
someone need fixes in RN, example: fix typo, this wouldn't require vote
right?



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Apr 17, 2014 at 12:03 PM, sebgoa  wrote:

>
> On Apr 17, 2014, at 5:57 PM, David Nalley  wrote:
>
> > Are you shipping (e.g. making source available for download) tarballs
> > or merely producing documentation that we publish publicly.
> > If the answer to that is no; then we don't need votes or a formal
> > release process (anymore than we need votes for publishing content to
> > cloudstack.apache.org
>
> -sources are available through the asf git repo and the github mirror.
> -we do not make docs tar ball or packages.
> -we do build pdf and potentially epub that people can download
>
> As a matter of fact since the build and publishing platform is external to
> ASF infra, we (I since it's my RTD account) are just consuming the docs
> from git and providing it to the community like we do with .debs and .rpms .
>
> Good point David,
>
> >
> > --David
> >
> > On Thu, Apr 17, 2014 at 11:43 AM, sebgoa  wrote:
> >>
> >> On Apr 17, 2014, at 5:31 PM, Pierre-Luc Dion 
> wrote:
> >>
> >>> Should we have a page on wiki explaining how we would handle
> release-notes
> >>> on RTD ? and then vote on the method?
> >>> I'm not seeing other alternative to branches exept having one RTD
> project
> >>> for each release-notes.
> >>>
> >>
> >> I think your email here explains it well.
> >>
> >> What we need now is a [DISCUSS] thread on whether we want to vote on
> docs releases and whether we need a formal release process or not ?
> >>
> >> Do you want to start that thread ;)
> >>
> >>>
> >>>
> >>>
> >>>
> >>> Pierre-Luc Dion
> >>> Architecte de Solution Cloud | Cloud Solutions Architect
> >>> 855-OK-CLOUD (855-652-5683) x1101
> >>> - - -
> >>>
> >>> *CloudOps*420 rue Guy
> >>> Montréal QC  H3J 1S6
> >>> www.cloudops.com
> >>> @CloudOps_
> >>>
> >>>
> >>> On Tue, Apr 15, 2014 at 12:28 PM, David Nalley  wrote:
> >>>
> >>>> So I think it makes sense for most documents to point to feature
> >>>> version (e.g. 4.3 branch, 4.4 branch.) E.g. docs for 4.3.1 should be
> >>>> materially the same as 4.3.0 from a docs standpoint. Release notes are
> >>>> the exception here, though perhaps they could be dealt with in an
> >>>> additive way.
> >>>>
> >>>> --David
> >>>>
> >>>> On Tue, Apr 15, 2014 at 11:17 AM, sebgoa  wrote:
> >>>>> To add to what Pierre-Luc said:
> >>>>>
> >>>>> Readthedocs has something they call "releases" but those are in fact
> >>>> builds that point to a branch. Not a specific tag.
> >>>>>
> >>>>> So the release version of the doc we would see on the website will be
> >>>> the live state of the release branch, not a tag that we could vote on.
> >>>>>
> >>>>> That said, 

[DISCUSS] CloudStack Release-Notes docs on RTD

[Pierre-Luc Dion]

Since CS 4.3 release notes are on RST format hosted on
readthedocs.org(RTD) and available from github repo.

RTD allow us to provide version of documentation to follow the software
version by using git branches or tags.

In order to provide Release notes for multiple CloudStack Version we would
use Git Branches in the RN gitrepo (
https://github.com/apache/cloudstack-docs-rn) for each CloudStack Release.
 master would be use the the next version and will not be visible on RTD.

Sebastien did update the GIT repo to create the branch 4.3 which is now the
default visible release-note on RTD. so now if you look at the release note
the version is 4.3 and not latest.

I will use the master branch to start the Release note of 4.4, if we need
to apply correction to the 4.3 release note we could do it in the branch
4.3 or in master and cherrypick.

In the case we would have 2 releases in progress in the same time (ex:
4.3.1) we could have a new branch 4.3.1 and update this branch directly.

ref: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

4.4 release-notes

[Pierre-Luc Dion]

Hi all,

I'll help on the Release-notes of 4.4.  Could it be possible to provide a
list of new features in 4.4 or point me where I can get it ?  Their is a
public filter in JIRA but I'm not sure it is accurate.

Also, on the upgrade notes side, does it require special step like
upgrading to a new SystemVM templates?

BTW, how can I create shared/public issues filter in JIRA in order to
generate know issues and fixed issues for this release?

in case someone could create them:
4.4.0 Fixed Issues
project = CLOUDSTACK AND type = Bug AND affectedVersion in (4.2.0, 4.2.1,
4.3.0) AND fixVersion = 4.4.0 AND resolution != "\"Unresolved\"" ORDER BY
created DESC, priority DESC, key ASC

4.4.0 Known Issues
project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.0 OR
fixVersion = 4.4.0) AND resolution is EMPTY AND level = "Public" ORDER BY
priority DESC, key ASC

Thank you!

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: 4.4 release-notes

[Pierre-Luc Dion]

Thanks for you help Daan,

It would be best if filters could be publically accessible so the RN script
would work, if you can do this. I can't, from Jira doc I would not be allow
to do that but some person ca since 4.3 filters exists.


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Mon, May 5, 2014 at 3:19 PM, Daan Hoogland wrote:

> Pierre-Luc,
>
> I made a copy of
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12323241
> and added your filters. I don't know how to share them with you, yet.
> Maybe I don't need to; it's at
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12323265
> see if you can reach it. Let me know if it is as private as it claims
> to be.
>
> Daan
>
> On Mon, May 5, 2014 at 8:52 PM, Daan Hoogland 
> wrote:
> > Animesh,
> >
> > Can you (give me rights to) add these filters to the release dashboard?
> >
> > On Fri, May 2, 2014 at 4:43 AM, Pierre-Luc Dion 
> wrote:
> >> 4.4.0 Fixed Issues
> >> project = CLOUDSTACK AND type = Bug AND affectedVersion in (4.2.0,
> 4.2.1,
> >> 4.3.0) AND fixVersion = 4.4.0 AND resolution != "\"Unresolved\"" ORDER
> BY
> >> created DESC, priority DESC, key ASC
> >>
> >> 4.4.0 Known Issues
> >> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.0 OR
> >> fixVersion = 4.4.0) AND resolution is EMPTY AND level = "Public" ORDER
> BY
> >> priority DESC, key ASC
> >>
> >
> >
> >
> > --
> > Daan
>
>
>
> --
> Daan
>

Re: 4.4 release-notes

[Pierre-Luc Dion]

Request Created under ASF infrastructure team; INFRA project.

Thanks David,


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Mon, May 5, 2014 at 4:17 PM, David Nalley  wrote:

> You'll need to file a ticket with infra.
>
> On Mon, May 5, 2014 at 2:52 PM, Daan Hoogland 
> wrote:
> > Animesh,
> >
> > Can you (give me rights to) add these filters to the release dashboard?
> >
> > On Fri, May 2, 2014 at 4:43 AM, Pierre-Luc Dion 
> wrote:
> >> 4.4.0 Fixed Issues
> >> project = CLOUDSTACK AND type = Bug AND affectedVersion in (4.2.0,
> 4.2.1,
> >> 4.3.0) AND fixVersion = 4.4.0 AND resolution != "\"Unresolved\"" ORDER
> BY
> >> created DESC, priority DESC, key ASC
> >>
> >> 4.4.0 Known Issues
> >> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.0 OR
> >> fixVersion = 4.4.0) AND resolution is EMPTY AND level = "Public" ORDER
> BY
> >> priority DESC, key ASC
> >>
> >
> >
> >
> > --
> > Daan
>

Re: 4.4 release-notes

[Pierre-Luc Dion]

Daan, you should be able to create public issue filters.

Please refer to the case with INFRA,
https://issues.apache.org/jira/browse/INFRA-7679

Thanks,


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, May 6, 2014 at 9:16 AM, David Nalley  wrote:

> Animesh had to be granted karma on Jira to share filters/dashboards.
>
> --David
>
>
> On Tue, May 6, 2014 at 9:10 AM, Sebastien Goasguen 
> wrote:
>
> >
> > On May 6, 2014, at 4:34 AM, Daan Hoogland 
> wrote:
> >
> > > I think Pierre-Luc's idea is good and infra will surely pick up the
> > > ticket one of these days. The dashboard is Animesh's work. I think he
> > > used private filters.
> >
> > I agree, I built the RN for 4.3 based on animesh filters.
> >
> > I am just wondering why this needs special karma or that the filters are
> > private.
> >
> > >
> > > On Tue, May 6, 2014 at 10:19 AM, Sebastien Goasguen 
> > wrote:
> > >> Maybe we can ask animesh how he did it for 4.3 ...
> > >>
> > >> -sebastien
> > >>
> > >>
> > >> On Mon, May 5, 2014 at 4:35 PM, Pierre-Luc Dion 
> > wrote:
> > >>
> > >>> Request Created under ASF infrastructure team; INFRA project.
> > >>>
> > >>> Thanks David,
> > >>>
> > >>>
> > >>> Pierre-Luc Dion
> > >>> Architecte de Solution Cloud | Cloud Solutions Architect
> > >>> 855-OK-CLOUD (855-652-5683) x1101
> > >>> - - -
> > >>>
> > >>> *CloudOps*420 rue Guy
> > >>> Montréal QC  H3J 1S6
> > >>> www.cloudops.com
> > >>> @CloudOps_
> > >>>
> > >>>
> > >>> On Mon, May 5, 2014 at 4:17 PM, David Nalley  wrote:
> > >>>
> > >>>> You'll need to file a ticket with infra.
> > >>>>
> > >>>> On Mon, May 5, 2014 at 2:52 PM, Daan Hoogland <
> > daan.hoogl...@gmail.com>
> > >>>> wrote:
> > >>>>> Animesh,
> > >>>>>
> > >>>>> Can you (give me rights to) add these filters to the release
> > dashboard?
> > >>>>>
> > >>>>> On Fri, May 2, 2014 at 4:43 AM, Pierre-Luc Dion <
> pd...@cloudops.com>
> > >>>> wrote:
> > >>>>>> 4.4.0 Fixed Issues
> > >>>>>> project = CLOUDSTACK AND type = Bug AND affectedVersion in (4.2.0,
> > >>>> 4.2.1,
> > >>>>>> 4.3.0) AND fixVersion = 4.4.0 AND resolution != "\"Unresolved\""
> > ORDER
> > >>>> BY
> > >>>>>> created DESC, priority DESC, key ASC
> > >>>>>>
> > >>>>>> 4.4.0 Known Issues
> > >>>>>> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.0
> OR
> > >>>>>> fixVersion = 4.4.0) AND resolution is EMPTY AND level = "Public"
> > ORDER
> > >>>> BY
> > >>>>>> priority DESC, key ASC
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Daan
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> ---
> > >> Sebastien Goasguen
> > >> Open Source Cloud Evangelist, Cloudstack
> > >> http://sites.google.com/site/runseb/
> > >
> > >
> > >
> > > --
> > > Daan
> >
> >
>

CLOUDSTACK-6092 in 4.4 ?

[Pierre-Luc Dion]

does this new Feature will be in 4.4 ?

in JIRA status is currently : In Progress

Thanks

Pierre-Luc Dion

Re: [ACS 4.4] ETA until RC1

[Pierre-Luc Dion]

Speaking of RN, is there any place where we can find new features in order
to build this release-notes?

Does Jira filter like this is enough?
project = CLOUDSTACK AND type = "New Feature" AND fixVersion = 4.4.0 ORDER
BY priority DESC, key ASC

Also, do we need new system vm templates? do we have new hypervisor version
supported?

Thanks,



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, May 13, 2014 at 1:20 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Yep, that's definitely true, Sebastien.
>
> I just wanted to get everyone on the same page for expectations around a
> date for RC1...even if we're still looking at it being a couple weeks out.
>
> The initial RC date came and went last Friday, so I just wanted to do a
> "sanity check" around when we can realistically expect this to happen.
>
>
> On Tue, May 13, 2014 at 7:53 AM, sebgoa  wrote:
>
> >
> > On May 13, 2014, at 10:22 AM, Daan Hoogland 
> > wrote:
> >
> > > thanks for chopping my...
> > >
> > > I have no idea what so ever. The number of blokkers has been stable
> > > just over ten over the last few weeks. The list has not been stable so
> > > a lot of new issues have been popping up. Also the update times are at
> > > most a week old. Silver side of the coin is that the number of
> > > critical and major issues have steadily dropped:)
> >
> > Before cutting an RC, we need Release Notes (i.e list of features)
> > And we probably need devcloud running properly to have a release
> procedure.
> >
> > my .2 cts
> >
> > >
> > > On Mon, May 12, 2014 at 7:02 PM, Mike Tutkowski
> > >  wrote:
> > >> Hi Daan,
> > >>
> > >> I know we still have several blocker bugs that need to be addressed
> > before
> > >> we consider creating RC1 for 4.4.
> > >>
> > >> Any thoughts (or hopes) on when we might realistically be able to spin
> > up
> > >> RC1?
> > >>
> > >> Thanks!
> > >>
> > >> --
> > >> *Mike Tutkowski*
> > >> *Senior CloudStack Developer, SolidFire Inc.*
> > >> e: mike.tutkow...@solidfire.com
> > >> o: 303.746.7302
> > >> Advancing the way the world uses the
> > >> cloud<http://solidfire.com/solution/overview/?video=play>
> > >> *™*
> > >
> > >
> > >
> > > --
> > > Daan
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>

Re: Modern template hosting

[Pierre-Luc Dion]

hi!

I think we should work with distro provider to have their cloud builds work
with cloudstack. Good example is CoreOS, it work out of the box from their
channel builds.
it shouldn't be too complicated to have centos, ubuntu and debian, unless
...

For our systemvm templates, can we just change the URL for somthing like
cloudstack.apache.org/systemvm/... ?
and for old systemvm that are depricated but that we might want to keep,
could we archive them into a github repo in
https://github.com/apachecloudstack ?




On Mon, Feb 27, 2017 at 6:28 PM, Chiradeep Vittal 
wrote:

> My stance is that the current workflow does a disservice to the user
> community by letting them install / use outdated and insecure templates.
> Now, let's assume download.cloud.com is gone forever. What do we tell ACS
> users pre-4.11 as far as *built-in templates* go?
> 1. Direct them to update templates.sql with some new URL, but with the same
> dirty old templates
> 2. Direct them to update templates.sql with some new URL, but with nice
> templates (e.g., open.vm.eu)
> 3. Same as (2), but document more choices.
>
> Now, why should things be different for 4.11 and later? Documenting the
> steps to install templates offline is trivial (and can be scripted to a
> large part, like cloud-install-sys-tmplt)
>
> For pre-4.11 users, for *systemvms*, anyway we tell them to use
> http://cloudstack.apt-get.eu which is not controlled by ACS.
>
>
> On Mon, Feb 27, 2017 at 2:50 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Agree with you.
> > We need to support the current working flow. And then, define the first
> > version that will start using the new approach.
> >
> > On Mon, Feb 27, 2017 at 5:36 PM, Will Stevens 
> > wrote:
> >
> > > I think we almost need a two pronged approach.
> > >
> > > 1) Get a solution in place which will enable us to document and serve
> > > templates for legacy systems.  I will work on this.
> > > 2) Discuss and understand how we SHOULD be handling this problem in the
> > > future and in what release we can expect it.
> > >
> > > I think we need to do both.  I think we should start to try to really
> > > understand what we want to deliver in (2) going forward.
> > >
> > > *Will STEVENS*
> > > Lead Developer
> > >
> > > 
> > >
> > > On Mon, Feb 27, 2017 at 4:53 PM, Rafael Weingärtner <
> > > rafaelweingart...@gmail.com> wrote:
> > >
> > > > My worry is exactly with system VMs templates.
> > > >
> > > > Currently, we indicate administrators to download them from
> > > > http://cloudstack.apt-get.eu/systemvm/4.6/ [1]. However, the
> > > installation
> > > > docs do not mention the expected hashes for the file that is going to
> > be
> > > > downloaded.
> > > > Also, I do not know the code that downloads system VMs templates
> (when
> > > > upgrading), but if the hash being checked is taken from the mirror
> used
> > > to
> > > > download the file; the only thing it checks is that if the download
> > > > finished successfully (no transmission errors). If we want to check
> > > > integrity, check that the template we created is untampered; we need
> to
> > > > host and serve the hash in a secure manner.
> > > >
> > > > [1]
> > > > http://docs.cloudstack.apache.org/projects/cloudstack-
> > > installation/en/4.9/
> > > > management-server/index.html#prepare-the-system-vm-template
> > > >
> > > >
> > > > On Mon, Feb 27, 2017 at 4:36 PM, Chiradeep Vittal <
> > chirade...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hashes are checked (md5 IIRC) today.
> > > > > But given the issues, I think the project should steer away from
> > > hosting
> > > > > templates except the systemvm template.
> > > > >
> > > > > On Mon, Feb 27, 2017 at 1:31 PM, Rafael Weingärtner <
> > > > > rafaelweingart...@gmail.com> wrote:
> > > > >
> > > > > > Will, I think we could support different path structures. This
> can
> > > > > > facilitate different deployment of mirrors based on the structure
> > the
> > > > > host
> > > > > > has.
> > > > > >
> > > > > > Could I add something else to the discussion? Have we discussed
> the
> > > > > > security impacts of setting up this mirrors approach?
> > > > > > I mean, if any of the mirrors gets corrupted (let`s say by a
> > hacker),
> > > > and
> > > > > > the templates are injected with malicious code, an attacker could
> > > > > > potentially get un-monitored and unlimited access to a cloud
> > > > environment.
> > > > > >
> > > > > > If we assume that the mirror may get malicious (it is not that I
> do
> > > not
> > > > > > trust you guys, but bad things happen), we cannot host hashes
> > there.
> > > > > Where
> > > > > > do you think we could store Sha512 or another hash type for these
> > > > > > templates? Could we host in the newly proposed Github repo or
> maybe
> > > > some
> > > > > > place in the ACS website?
> > > > > >
> > > > > > This would have an impact on clients (needing clear
> documentation)
> > > and
> > > > > our
> > > > > > code that aut

Re: :[VOTE] Apache Cloudstack 4.10.0.0

[Pierre-Luc Dion]

Do we support  centos6  with this 4.10 on jdk8?

Because I did not had much success to install 4.10 jdk8 on centos6  and it
would make more sense to drop support of centos6 so our packages would use
centos7 with distro packages for tomcat7 and jdk8.  Should also be the same
with ubuntu 16.04 that use jdk8 and tomcat7 by default ?


thanks,


On Wed, Mar 1, 2017 at 9:01 AM, Rene Moser  wrote:

> Hi
>
> While not be directly related to the clodustack java source code, any
> RPM created using the specs from the repo e.g. from packages/centos7
> and proceeding an upgrade, will hit CLOUDSTACK-9765, PR
> https://github.com/apache/cloudstack/pull/1923 fixes the issue.
>
> Regards
> René
>
>
> On 03/01/2017 02:12 AM, Rajani Karuturi wrote:
> > Hi All,
> >
> > I've created a 4.10.0.0 release, with the following artifacts up for a
> vote:
> >
> > Git Branch and Commit
> > SH:https://git-wip-us.apache.org/repos/asf?p=cloudstack.
> git;a=shortlog;h=refs/heads/4.10.0.0-RC20170301T0634
> > Commit:7c1d003b5269b375d87f4f6cfff8a144f0608b67
> >  git;a=shortlog;h=refs/heads/4.10.0.0-RC20170301T0634Commit:
> 7c1d003b5269b375d87f4f6cfff8a144f0608b67>
> >
> > Source release (checksums and signatures are available at the same
> > location):https://dist.apache.org/repos/dist/dev/cloudstack/4.10.0.0/
> >
> > PGP release keys (signed using
> > CBB44821):https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> >
> >
> > ~Rajani
> > http://cloudplatform.accelerite.com/
> >
>

Re: :[VOTE] Apache Cloudstack 4.10.0.0

[Pierre-Luc Dion]

nableAdapter.
> call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-2:ctx-bc104380
> job-25/job-27) (logid:aab9c320) Remove job-27 from job monitoring
> WARN  [o.a.c.alerts] (API-Job-Executor-1:ctx-f787201d job-25
> ctx-56356c1a) (logid:aab9c320)  alertType:: 8 // dataCenterId:: 1 //
> podId:: 1 // clusterId:: null // message:: Failed to deploy Vm with Id: 6,
> on Host with Id: null
> ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-1:ctx-f787201d
> job-25) (logid:aab9c320) Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin
> com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due
> to insufficient capacity
> at com.cloud.vm.VirtualMachineManagerImpl.start(
> VirtualMachineManagerImpl.java:623)
> at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.
> deployVirtualMachine(VMEntityManagerImpl.java:242)
> at org.apache.cloudstack.engine.cloud.entity.api.
> VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:212)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(
> UserVmManagerImpl.java:4084)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(
> UserVmManagerImpl.java:3682)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(
> UserVmManagerImpl.java:3670)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:333)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:190)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:157)
> at org.apache.cloudstack.network.contrail.management.
> EventUtils$EventInterceptor.invoke(EventUtils.java:107)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:168)
> at com.cloud.event.ActionEventInterceptor.invoke(
> ActionEventInterceptor.java:51)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:168)
> at org.springframework.aop.interceptor.ExposeInvocationInterceptor.
> invoke(ExposeInvocationInterceptor.java:92)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:179)
> at org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:213)
> at com.sun.proxy.$Proxy186.startVirtualMachine(Unknown Source)
> at org.apache.cloudstack.api.command.admin.vm.
> DeployVMCmdByAdmin.execute(DeployVMCmdByAdmin.java:50)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at com.cloud.api.ApiAsyncJobDispatcher.runJob(
> ApiAsyncJobDispatcher.java:108)
> at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.
> runInContext(AsyncJobManagerImpl.java:554)
> at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(
> ManagedContextRunnable.java:49)
> at org.apache.cloudstack.managed.context.impl.
> DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.
> callWithContext(DefaultManagedContext.java:103)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.
> runWithContext(DefaultManagedContext.java:53)
> at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(
> ManagedContextRunnable.java:46)
> at org.apache.cloudstack.framework.jobs.impl.
> AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:502)
> at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.cloud.exception.InsufficientServerCapacityException:
> Unable to create a deployment for VM[User|i-2-6-VM]Scope

Re: :[VOTE] Apache Cloudstack 4.10.0.0

[Pierre-Luc Dion]

e a new table: cloud.storage_pool_tags.
> > >
> > > The addition of this table seems to have broken the
> > listStorageTags API command. When this command runs, it
> doesn’t pick up any
> > storage tags for me (and I know I have one storage tag).
> > >
> > > This data used to be stored in the
> cloud.storage_pool_details
> > table. It’s good to put it in its own table, but will our
> upgrade process
> > move the existing tags from storage_pool_details to
> storage_pool_tags?
> > >
> > > I have not yet opened a ticket for this. I want to examine
> it
> > a bit more before doing so.
> > >
> > > On 3/7/17, 8:10 AM, "Tutkowski, Mike" <
> > mike.tutkow...@netapp.com> wrote:
> > >
> > > No VM snapshot.
> > >
> > > I tried while the VM was in the Running state and then I
> > also tried in the Stopped state. Same results.
> > >
> > >> On Mar 7, 2017, at 7:54 AM, Sergey Levitskiy <
> > sergey.levits...@autodesk.com> wrote:
> > >>
> > >> Is VM has an VMsnaphsot? Is VM in Stopped state?
> > >>
> > >> On 3/6/17, 10:32 PM, "Tutkowski, Mike"
> 
> > wrote:
> > >>
> > >> I seem to have found another blocker:
> > >>
> > >> https://issues.apache.org/jira/browse/CLOUDSTACK-9822
> > >>
> > >> On 3/6/17, 9:51 PM, "Rajani Karuturi" 
> wrote:
> > >>
> > >> PRs are ready for the blockers. Waiting for reviews and
> test
> > >> results. Once they are ready, I will merge them(and a few
> more
> > >> bug fixes) and create RC2 (probably tomorrow, Wednesday)
> > >>
> > >> Thanks,
> > >>
> > >> ~ Rajani
> > >>
> > >> http://cloudplatform.accelerite.com/
> > >>
> > >> On March 3, 2017 at 4:30 PM, Rajani Karuturi (
> > raj...@apache.org)
> > >> wrote:
> > >>
> > >> I will create RC2 on Monday with the fixes mentioned in my
> > >> previous mail.
> > >>
> > >> ~ Rajani
> > >>
> > >> http://cloudplatform.accelerite.com/
> > >>
> > >> On March 3, 2017 at 2:36 PM, Rohit Yadav
> > >> (rohit.ya...@shapeblue.com) wrote:
> > >>
> > >> Thanks Koushik, I did not realize Kishan had sent this
> > already.
> > >> Let's get either of the PRs merged and kick a RC2.
> > >>
> > >> Regards.
> > >>
> > >> 
> > >> From: Koushik Das 
> > >> Sent: 03 March 2017 14:14:56
> > >> To: dev@cloudstack.apache.org
> > >> Subject: Re: :[VOTE] Apache Cloudstack 4.10.0.0
> > >>
> > >> Looks like there is already a PR for the same issue
> > >> https://github.com/apache/cloudstack/pull/1982 from Kishan.
> > >>
> > >> -Koushik
> > >>
> > >> On 03/03/17, 1:58 PM, "Rohit Yadav" <
> > rohit.ya...@shapeblue.com>
> > >> wrote:
> > >>
> > >> -1 (binding)
> > >>
> > >> All, I've found an upgrade blocker. Pre 4.6 users are
> required
> > >> to seed 4.6 systemvmtemplate to proceed with the upgrade
> > >> otherwise upgrade fails, and from 4.9 upgrade to 4.10 does
> no
> > >> check/enforcement that 4.10 based systemvmtemplate has been
> > >> seeded/registered, nor the minimum required
> systemvmtemplate
> > >> version is changed from 4.6.0 to 4.10.0.
> > >>
> > >> After we have merged the strongswan/java8 PR, I had updated
> > the
> > >> upgrade docs on how to upgrade the systemvmtemplate here:
> > >>
> > >> http://docs.cloudstack.apache.org/projects/cloudstack-
> > release-notes/en/4.10/upgrade/upgrade-4.9.html
> > >>
> > >> Using the above, I've tried to fix these issues here,
> please
> > >> review and merge for RC2:
> > >>
> > >> https://github.com/apache/cloudstack/

Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare

[Pierre-Luc Dion]

Hi Syed, have you tried coud images from centos site, i think centos build
cloudimage as canonical for ubuntu.


On Mar 30, 2017 5:24 PM, "Rafael Weingärtner" 
wrote:

> Attachments are not forwarded with emails.
>
> On Thu, Mar 30, 2017 at 5:16 PM, Syed Ahmed  wrote:
>
> > FYI I'm attaching the screenshot of the cloud-init error
> >
> >
> >
> > On Thu, Mar 30, 2017 at 5:14 PM, Syed Ahmed  wrote:
> > > Hi All,
> > >
> > > I'm trying to run a CentOS 7 template on VMWare and ACS 4.9 but
> > > somehow cloud-init doesn't seem to pick up the IP form the VR. The
> > > default template which is bundled with ACS (CentOS 5) works.
> > >
> > > I got the CentOS7 template from
> > > http://dl.openvm.eu/cloudstack/centos/vanilla/7/
> x86_64/CentOS-7-x86_64-
> > vanilla-vmware.ova
> > >
> > > Is there any setting that I need to do for this template? Are there
> > > any other places I can get a working template for CentOS7 for
> > > Cloudstack?
> > >
> > > Thanks,
> > > -Syed
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: :[VOTE] Apache Cloudstack 4.10.0.0

[Pierre-Luc Dion]

Look like we need a new systemvm named "systemvm-xenserver-4.10". t also
seams that older VR  ex: 4.7.x are still usable if the globalsetting
"minreq.sysvmtemplate.version" is changed after the first boot of
cloudstack-management that upgraded the database. I'll update the release
note acordingly...

So this 4.10 is looking promising! :-)




On Apr 1, 2017 16:02, "Pierre-Luc Dion"  wrote:

I'm testing upgrade to 4.10 from latest master. I have the following error
when upgrading from 4.7.2 in management-server.log:

2017-04-01 15:58:12,558 DEBUG [c.c.u.d.Upgrade4920to41000]
(localhost-startStop-1:null) (logid:) Updating System Vm template IDs
2017-04-01 15:58:12,561 DEBUG [c.c.u.d.Upgrade4920to41000]
(localhost-startStop-1:null) (logid:) Updating KVM System Vms
2017-04-01 15:58:12,561 WARN  [c.c.u.d.Upgrade4920to41000]
(localhost-startStop-1:null) (logid:) 4.10.0.0KVM SystemVm template not
found. KVM hypervisor is not used, so not failing upgrade
2017-04-01 15:58:12,562 DEBUG [c.c.u.d.Upgrade4920to41000]
(localhost-startStop-1:null) (logid:) Updating VMware System Vms
2017-04-01 15:58:12,563 WARN  [c.c.u.d.Upgrade4920to41000]
(localhost-startStop-1:null) (logid:) 4.10.0.0VMware SystemVm template not
found. VMware hypervisor is not used, so not failing upgrade
2017-04-01 15:58:12,563 DEBUG [c.c.u.d.Upgrade4920to41000]
(localhost-startStop-1:null) (logid:) Updating XenServer System Vms
2017-04-01 15:58:12,565 ERROR [c.c.u.DatabaseUpgradeChecker]
(localhost-startStop-1:null) (logid:) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: 4.10.0.0XenServer SystemVm
template not found. Cannot upgrade system Vms
at com.cloud.upgrade.dao.Upgrade4920to41000.updateSystemVmTempl
ates(Upgrade4920to41000.java:195)
at com.cloud.upgrade.dao.Upgrade4920to41000.performDataMigratio
n(Upgrade4920to41000.java:64)
at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpg
radeChecker.java:426)
at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgra
deChecker.java:507)
at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif
eCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65)
at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif
eCycle.start(CloudStackExtendedLifeCycle.java:55)
at org.springframework.context.support.DefaultLifecycleProcesso
r.doStart(DefaultLifecycleProcessor.java:173)
at org.springframework.context.support.DefaultLifecycleProcesso
r.access$200(DefaultLifecycleProcessor.java:51)
at org.springframework.context.support.DefaultLifecycleProcesso
r$LifecycleGroup.start(DefaultLifecycleProcessor.java:346)
at org.springframework.context.support.DefaultLifecycleProcesso
r.startBeans(DefaultLifecycleProcessor.java:149)
at org.springframework.context.support.DefaultLifecycleProcesso
r.onRefresh(DefaultLifecycleProcessor.java:112)
at org.springframework.context.support.AbstractApplicationConte
xt.finishRefresh(AbstractApplicationContext.java:879)
at org.springframework.context.support.AbstractApplicationConte
xt.refresh(AbstractApplicationContext.java:545)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
at org.apache.cloudstack.spring.module.model.impl.DefaultModule
DefinitionSet.load(DefaultModuleDefinitionSet.java:79)
at org.apache.cloudstack.spring.module.factory.ModuleBasedConte
xtFactory.loadModules(ModuleBasedContextFactory.java:37)
at org.apache.cloudstack.spring.module.factory.CloudStackSpring
Context.init(CloudStackSpringContext.java:71)
at org.apache.cloudstack.spring.module.factory.CloudStackSpring
Context.(CloudStackSpringContext.java:58)
at org.apache.cloudstack.spring.module.factory.CloudStackSpring
Context.(CloudStackSpringContext.java:62)
at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.
contextInitialized(CloudStackContextLoaderListener.java:52)
at org.apache.catalina.core.StandardContext.listenerStart(Stand
ardContext.java:5068)
at org.apache.catalina.core.StandardContext.startInternal(Stand
ardContext.java:5584)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at org.apache.catalina.core.ContainerBase.addChildInternal(Cont
ainerBase.java:899)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
at org.apache.catalina.core.Standar

Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment

[Pierre-Luc Dion]

Yes, I saw people put a lot of efforts for it :-)

On Apr 5, 2017 10:20, "Rohit Yadav"  wrote:

> +1 in addition to my support for joining the experiment, I would also like
> us to have the option to assign labels on the PRs. Such labels can be
> useful for CIs and RMs to determine and merge PRs that are fully tested and
> blessed by reviewers.
>
>
> Regards.
>
> 
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> From: Rohit Yadav
> Sent: 05 April 2017 19:49:01
> To: dev
> Subject: Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment
>
>
> +1 looking forward to this.
>
> 
> From: Daan Hoogland 
> Sent: 05 April 2017 12:10:19
> To: dev
> Subject: [PROPOSAL] Apache Cloudstack should join the gitbox experiment
>
> In the Apache foundation an experiment has been going on to host
> mirrors of Apache project on github with more write access then just
> to the mirror-bot. For those projects committers can merge on github
> and put labels on PRs. I want to propose that we join that project and
> intend to start a vote on it here, soon.
>
> questions, thoughts?
>
> --
> Daan
>

Re: Alternative Cloudstack UI for KVM and Basic Zones (with SG)

[Pierre-Luc Dion]

Wow, that looks great, good start!

Do you have intent to give it back as an Apache projet eventually?

Thanks for the initiative!

Le 25 avr. 2017 4:04 PM, "Nathan Johnson"  a écrit :

> Very nice!
>
> Ivan Kudryavtsev  wrote:
>
> > Hello, Cloudstack community.
> >
> > We are proud to present our last development effort to you. During the
> last
> > 5 months we spend some time to develop alternative Cloudstack UI for
> basic
> > zones with KVM hypervisor and security groups. This is basically the
> thing
> > we are using in our clouds. During the design of the software we tried to
> > fulfill the expectations of our average cloud users and simplify
> operations
> > as much as possible.
> >
> > The project is OSS and can be found at GitHub with bunch of screenshots
> and
> > deployment guide. It's under active development so, we will ge glad if
> you
> > join and provide us with additional feedback, UX considerations and other
> > interesting information.
> >
> > Project page at GitHub: https://bwsw.github.io/cloudstack-ui/
> > Source code: https://github.com/bwsw/cloudstack-ui
> >
> > Have a good day. Looking forward hearing your feedback.
> >
> > --
> > With best regards, Ivan Kudryavtsev
> > Bitworks Software, Ltd.
> > Cell: +7-923-414-1515
> > WWW: http://bw-sw.com/
>
>
>

Re: Awesome CloudStack

[Pierre-Luc Dion]

Awesome! Great idea!

Le 12 mai 2017 4:17 AM, "Rohit Yadav"  a écrit :

> Nice, thanks for starting this and sharing René.
>
> Regards.
>
> 
> From: Rene Moser 
> Sent: 10 May 2017 22:53:55
> To: us...@cloudstack.apache.org; dev
> Subject: Awesome CloudStack
>
> Hi
>
> I started "A curated list of bookmarks, packages, tutorials, videos and
> other cool resources from the CloudStack ecosystem" on
> https://github.com/resmo/awesome-cloudstack
>
> Feel free to extend it by sending PRs ;)
>
> René
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] Config Drive: Using the OpenStack format?

[Pierre-Luc Dion]

Is this a format that would work for all hypervisor supported  by
cloudstack? Because openstack is highly focus on kvm.

Also,did anyone verified if that would work for coreos and
cloudbase-init(cloud-init for Windows)

Otherwise I like the idea of removing the VR dependency.

Le 22 mai 2017 7:40 AM, "Nux!"  a écrit :

> +1 using openstack format
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Wido den Hollander" 
> > To: "dev" , "Kris Sterckx" <
> kris.ster...@nuagenetworks.net>
> > Sent: Friday, 19 May, 2017 14:15:28
> > Subject: [DISCUSS] Config Drive: Using the OpenStack format?
>
> > Hi,
> >
> > Yesterday at ApacheCon Kris from Nuage networks gave a great
> presentation about
> > alternatives for userdata from the VR: Config Drive
> >
> > In short, a CD-ROM/ISO attached to the Instance containing the
> meta/userdata
> > instead of having the VR serve it.
> >
> > The outstanding PR [0] uses it's own format on the ISO while cloud-init
> already
> > has support for config drive [1].
> >
> > This format uses 'openstack' in the name, but it seems to be in
> cloud-init
> > natively and well supported.
> >
> > I started the discussion yesterday during the talk and thought to take
> it to the
> > list.
> >
> > My opinion is that we should use the OpenStack format for the config
> drive:
> >
> > - It's already in cloud-init
> > - Easier to templates to be used on CloudStack
> > - Easier adoption
> >
> > We can always write a file like "GENERATED_BY_APACHE_CLOUDSTACK" or
> something on
> > the ISO.
> >
> > We can also symlink the 'openstack' directory to a directory called
> 'cloudstack'
> > on the ISO.
> >
> > Does anybody else have a opinion on this one?
> >
> > Wido
> >
> > [0]: https://github.com/apache/cloudstack/pull/2097
> > [1]:
> > http://cloudinit.readthedocs.io/en/latest/topics/
> datasources/configdrive.html#version-2
>

[DISCUSS] drop support for CentOS6 with 4.10

[Pierre-Luc Dion]

Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
management-server and usage ?

all the Upgrade path tests I've made was by creating new management server
on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
install well on centos7 and I'm not away somebody test them on centos6.

Should we call a vote on this?  I'm writing the upgrade part of the release
notes and I would focus on centos7 only. we should also update our Quick
Install Guide...


Thanks,

PL

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Pierre-Luc Dion]

In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
to provide some instruction on how to install it, and is there anyone that
tested 4.10 packages on CentOS6 ?

Cheers,

On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus 
wrote:

> I would suggest that this would justify a 5.0 release.. might be a good
> time to get in any other major changes
>
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> Sent: 09 July 2017 13:46
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS] drop support for CentOS6 with 4.10
>
> Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> management-server and usage ?
>
> all the Upgrade path tests I've made was by creating new management server
> on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> install well on centos7 and I'm not away somebody test them on centos6.
>
> Should we call a vote on this?  I'm writing the upgrade part of the
> release notes and I would focus on centos7 only. we should also update our
> Quick Install Guide...
>
>
> Thanks,
>
> PL
>

[4.10] repos

[Pierre-Luc Dion]

Hi,

I've created new jenkins jobs [1] to create package for our release, The
jobs pushed rpm's but for systemvm, look like there is a wget job somewhere
that download systemvm template from jenkins from build of master branch,
I've created a set of systemvm templates that I would like to published on
download.cloudstack.org but they are most likely going to be overwritten,
could we disable that job ?

[1] https://builds.cloudstack.org/view/release/

PL

access to github

[Pierre-Luc Dion]

Hi,

His there a particular process to follow to have access to github for
documentation projects?
Could it be possible Github is not a mirror anymore since the apache repo
[1] doesn't seams to exist ?

[1] git://git.apache.org/cloudstack-docs-admin.git

Thanks,

Pierre-Luc

Re: access to github

[Pierre-Luc Dion]

Hi Will,

Not sure what  was visible  with the Pony mail link, doesn't seams to work.
but anyway , I'll check for the gitbox projet,
There is some PRs I'd like to merge into the documentation.

Thanks !



*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Wed, Aug 2, 2017 at 8:45 PM, Will Stevens 
wrote:

> Here you go.
>
> https://lists.apache.org/thread.html/9fb5894da34e2cc383b2f9b01ab239
> fd7a5131b90f67c282560ffc5f@
> 
>
> On Aug 2, 2017 8:42 PM, "Will Stevens"  wrote:
>
> > You have to 2FA enabled in your GitHub account and register for the
> gitbox
> > project to be able to commit to that. But you can create a PR for now
> and I
> > can work with you to make sure you get your committee access setup.
> >
> > On Aug 2, 2017 8:39 PM, "Will Stevens"  wrote:
> >
> >> I think your looking for this. No?
> >>
> >> https://github.com/apache/cloudstack-docs-admin
> >>
> >> On Aug 2, 2017 8:37 PM, "Pierre-Luc Dion"  wrote:
> >>
> >>> Hi,
> >>>
> >>> His there a particular process to follow to have access to github for
> >>> documentation projects?
> >>> Could it be possible Github is not a mirror anymore since the apache
> repo
> >>> [1] doesn't seams to exist ?
> >>>
> >>> [1] git://git.apache.org/cloudstack-docs-admin.git
> >>>
> >>> Thanks,
> >>>
> >>> Pierre-Luc
> >>>
> >>
>

Re: cloud-set-guest-password working with systemctl

[Pierre-Luc Dion]

Has Syed is saying its most likely because of systemd. Have you try to use
cloud-init? It work well but need some tuning for password and sshkey
reset...



Le 7 août 2017 09:33, "Syed Ahmed"  a écrit :

> Hi,
>
> Is the password server mentioned in the logs 192.168.155.1 reachable? The
> password server is hosted on the VR. Sometimes, restarting the network will
> reboot the VR and fix this. If not let us know, we'll help you out.
>
> Thanks,
> -Syed
>
> On Fri, Aug 4, 2017 at 9:33 AM, Marc Poll Garcia <
> marc.poll.gar...@upcnet.es
> > wrote:
>
> > Hello everyone,
> >
> > last days we are experiencing some issues on our "Ubuntu 16.04" template,
> > created step by step following this tutorial:
> >
> > http://docs.cloudstack.apache.org/projects/cloudstack-
> > administration/en/4.8/templates/_create_linux.html
> >
> > It is happening on "Ubuntu 16.04.2 LTS \n \l" system and  "CloudStack
> > 4.9.2.0" version.
> >
> >
> > Unfortunately we detected that some of the features we had, no longer
> work,
> > such as the changing password one.
> >
> > After several test and reviewing it more deeply, i see that it works
> > "intermittently" and the service sometimes does not start on boot:
> >
> > /etc/init.d/cloud-set-guest-password status
> > ● cloud-set-guest-password.service - LSB: Init file for Password
> Download
> > Client
> >Loaded: loaded (/etc/init.d/cloud-set-guest-password; bad; vendor
> > preset: enabled)
> >Active: *failed* (Result: exit-code) since Thu 2017-08-03 16:09:09
> CEST;
> > 39min ago
> >  Docs: man:systemd-sysv-generator(8)
> >
> > Aug 03 16:08:58 Ubuntu16PassKO systemd[1]: Starting LSB: Init file for
> > Password Download Client...
> > Aug 03 16:08:58 Ubuntu16PassKO cloud-set-guest-password[1062]:  *
> Starting
> > cloud cloud-set-guest-password
> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1252]: DHCP file
> > (/var/lib/dhcp/dhclient-ens160.leases) exists. No need to restart
> > dhclient.
> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1256]: Using DHCP lease from
> > /var/lib/dhcp/dhclient-ens160.leases
> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1263]: Found password server IP
> > 192.168.155.1 in /var/lib/dhcp/dhclient-ens160.leases
> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1264]: Sending request to password
> > server at 192.168.155.1
> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]:
> > cloud-set-guest-password.service: *Control process exited, code=exited
> > status=4*
> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]: *Failed to start LSB: *Init
> file
> > for Password Download Client.
> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]:
> > cloud-set-guest-password.service: Unit entered failed state.
> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]:
> > cloud-set-guest-password.service: Failed with result 'exit-code'.
> >
> >
> > LSB part from the script:
> >
> > root@Uprovav1:~# head -n20 /etc/init.d/cloud-set-guest-password
> >
> > #!/bin/bash
> >
> > #
> >
> > # Init file for Password Download Client
> >
> > #
> >
> > ### BEGIN INIT INFO
> >
> > # Provides: cloud-set-guest-password
> >
> > # Required-Start:   $local_fs $syslog $network
> >
> > # Required-Stop:$local_fs $syslog $network
> >
> > # Default-Start:2 3 4 5
> >
> > # Default-Stop: 0 1 6
> >
> > # Short-Description:Init file for Password Download Client
> >
> > ### END INIT INFO
> >
> >
> > Is it happening to anyone else? Is there another compatible version from
> > this script?
> >
> > Or maybe we have to adapt it to the new "systemctl"
> >
> > Thanks in advance.
> >
> > --
> > Marc Poll Garcia
> > Technology Infrastructure . Àrea de Serveis TIC
> > Telèfon:  93.405.43.57
> >
> > [image: UPCnet]
> >
> > --
> > Aquest correu electrònic pot contenir informació confidencial o legalment
> > protegida i està exclusivament dirigit a la persona o entitat
> destinatària.
> > Si vostè no és el destinatari final o persona encarregada de recollir-lo,
> > no està autoritzat a llegir-lo, retenir-lo, modificar-lo, distribuir-lo,
> > copiar-lo ni a revelar el seu contingut. Si ha rebut aquest correu
> > electrònic per error, li preguem que informi al remitent i elimini del
> seu
> > sistema el missatge i el material annex que pugui contenir.
> > Gràcies per la seva col.laboració.
> > --
> >
> > *** Si us plau, no m'imprimeixis. Vull seguir sent digital ***
> > *** Por favor, no me imprimas. Quiero seguir siendo digital ***
> > *** Please, don't print me. I want to remain digital ***
> > --
> >
>

Re: cloud-set-guest-password working with systemctl

[Pierre-Luc Dion]

Hi,

On my side we use cloud-init in all our Linux templates. We got it to work
for password, password-reset, sshkey and sshkey-reset. It also support
user-data, and provide an easy way to manage a different user than root.

I think our community documentation need an update on this topic...

Cheers,

Le 28 août 2017 5:29 PM, "Sebastian Gomez"  a écrit :

I had the same problem like Marc and I could not resolve it on Ubuntu 16.04.
I followed the cloudstack steps to set it up, but the script is not running
well on our environment.

If I execute the script from command line, it works fine. During the boot
process, there is any problem on systemd and DHCP conjunction, and VR is
not reachable to reply this request.

On the other hand, I found many different versions of this OLD script, and
I remember that we had to use other community version also for Ubuntu
14.04. I noticed that this is a very old script, and has not been modified
for years.
As you proposed, I'm trying to do it via cloud-init. Just landed from
holidays I will finish this integration.

To do a so simply task like setting up a simple template is becoming a
nightmare, so *I would like to know how people *is setting Ubuntu templates
up?
- SSL key pairs? would be a good way, but Cloudstack 4.9.2 does not allow
to manage SSL key pairs using the GUI, only via API, so this is not a way
for not advanced users.
- Default user/password?


I can't believe that we are the only two buddies with this problem.



Regards.




Atentamente,
Sebastián Gómez

On Mon, Aug 7, 2017 at 3:36 PM, Pierre-Luc Dion  wrote:

> Has Syed is saying its most likely because of systemd. Have you try to use
> cloud-init? It work well but need some tuning for password and sshkey
> reset...
>
>
>
> Le 7 août 2017 09:33, "Syed Ahmed"  a écrit :
>
>> Hi,
>>
>> Is the password server mentioned in the logs 192.168.155.1 reachable? The
>> password server is hosted on the VR. Sometimes, restarting the network
>> will
>> reboot the VR and fix this. If not let us know, we'll help you out.
>>
>> Thanks,
>> -Syed
>>
>> On Fri, Aug 4, 2017 at 9:33 AM, Marc Poll Garcia <
>> marc.poll.gar...@upcnet.es
>> > wrote:
>>
>> > Hello everyone,
>> >
>> > last days we are experiencing some issues on our "Ubuntu 16.04"
>> template,
>> > created step by step following this tutorial:
>> >
>> > http://docs.cloudstack.apache.org/projects/cloudstack-
>> > administration/en/4.8/templates/_create_linux.html
>> >
>> > It is happening on "Ubuntu 16.04.2 LTS \n \l" system and  "CloudStack
>> > 4.9.2.0" version.
>> >
>> >
>> > Unfortunately we detected that some of the features we had, no longer
>> work,
>> > such as the changing password one.
>> >
>> > After several test and reviewing it more deeply, i see that it works
>> > "intermittently" and the service sometimes does not start on boot:
>> >
>> > /etc/init.d/cloud-set-guest-password status
>> > ● cloud-set-guest-password.service - LSB: Init file for Password
>> Download
>> > Client
>> >Loaded: loaded (/etc/init.d/cloud-set-guest-password; bad; vendor
>> > preset: enabled)
>> >Active: *failed* (Result: exit-code) since Thu 2017-08-03 16:09:09
>> CEST;
>> > 39min ago
>> >  Docs: man:systemd-sysv-generator(8)
>> >
>> > Aug 03 16:08:58 Ubuntu16PassKO systemd[1]: Starting LSB: Init file for
>> > Password Download Client...
>> > Aug 03 16:08:58 Ubuntu16PassKO cloud-set-guest-password[1062]:  *
>> Starting
>> > cloud cloud-set-guest-password
>> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1252]: DHCP file
>> > (/var/lib/dhcp/dhclient-ens160.leases) exists. No need to restart
>> > dhclient.
>> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1256]: Using DHCP lease from
>> > /var/lib/dhcp/dhclient-ens160.leases
>> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1263]: Found password server IP
>> > 192.168.155.1 in /var/lib/dhcp/dhclient-ens160.leases
>> > Aug 03 16:09:09 Ubuntu16PassKO cloud[1264]: Sending request to password
>> > server at 192.168.155.1
>> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]:
>> > cloud-set-guest-password.service: *Control process exited, code=exited
>> > status=4*
>> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]: *Failed to start LSB: *Init
>> file
>> > for Password Download Client.
>> > Aug 03 16:09:09 Ubuntu16PassKO systemd[1]:
>> > cloud-set-guest-password.service: Unit entered failed state.
>> > Aug 03 16

Re: Cluster anti-affinity

[Pierre-Luc Dion]

Hi Ivan,
I don't think cloudstack offer cluster anti affinity and i'm sure i would
be in favor of introducing another anti affinity level, because it would
expose cluster notion to your cloud user.

Although, look at the vm provisionning strategy config, their should be a
deployment strategy that would spread account vms across pods or clusters,
or prefer pod/cluster proximity. I think this could help you.

Regards,

Le 19 sept. 2017 01 h 57, "Ivan Kudryavtsev"  a
écrit :

> Hello, community. Right now cloudstack has affinity implementation for host
> anti-affinity and it's great and useful, but since the storage is often
> defined for a cluster (unless it's local or clustered like Ceph), it
> defined a failure domain. Does anybody experienced "cluster anti-affinity"
> implementation. Is it useful or were declined in the past by dev team? Any
> thoughts?
>
> How you tackle with VMs which should be completely independent and fault
> tolerant with shared storage (not Ceph)? I see that zone-level approach
> works for sure, but if the requirement is for intra-zone, I don't see the
> way to implement it, any thoughts?
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks Software, Ltd.
> Cell: +7-923-414-1515
> WWW: http://bitworks.software/ 
>

Re: Release packages for 4.9.3.0

[Pierre-Luc Dion]

I'll work something up this weekend...

we need some work on 4.10 I think...

On Thu, Sep 28, 2017 at 3:14 AM, Wido den Hollander  wrote:

>
> > Op 27 september 2017 om 8:30 schreef Özhan Rüzgar Karaman <
> oruzgarkara...@gmail.com>:
> >
> >
> > Hi Wido;
> > I checked http://cloudstack.apt-get.eu/ web site and 4.9.3 packages are
> > only under /ubuntu/dists/xenial/4.9/pool/ directory, for trusty there are
> > no packages available for 4.9.3 .
> >
> > This directory(/ubuntu/dists/xenial/4.9/pool/) also have 4.10 packages
> as
> > well, which i think they should not be there.
> >
> > When you have suitable time could you check the packages and its script.
> >
>
> Let me check that! Something must have gone wrong with the build and
> upload system. I'll check.
>
> Wido
>
> > Thanks
> > Özhan
> >
> > On Mon, Sep 25, 2017 at 7:24 AM, Rohit Yadav 
> > wrote:
> >
> > > Thanks Wido, can you help building and uploading of rpms as well. Maybe
> > > Pierre-Luc can help?
> > >
> > >
> > > - Rohit
> > >
> > > 
> > > From: Wido den Hollander 
> > > Sent: Thursday, September 21, 2017 1:09:49 PM
> > > To: Rohit Yadav; dev@cloudstack.apache.org; Pierre-Luc Dion
> > > Subject: Re: Release packages for 4.9.3.0
> > >
> > > Ah, sorry! The DEB packages should have been uploaded already :-)
> > >
> > > Wido
> > >
> > > > Op 21 september 2017 om 7:33 schreef Rohit Yadav <
> > > rohit.ya...@shapeblue.com>:
> > > >
> > > >
> > > > Ping - Wido/PL?
> > > >
> > > >
> > > > - Rohit
> > > >
> > > > 
> > > > From: Rohit Yadav 
> > > > Sent: Tuesday, September 12, 2017 5:44:36 PM
> > > > To: Wido den Hollander; Pierre-Luc Dion
> > > > Cc: dev@cloudstack.apache.org
> > > > Subject: Release packages for 4.9.3.0
> > > >
> > > > Wido/PL/others,
> > > >
> > > >
> > > > Can you please help with building and publishing of 4.9.3.0 rpms/deb
> > > packages on the download.cloudstack.org repository? I've built and
> > > published the repos on packages.shapeblue.com now (
> shapeblue.com/packages
> > > for details).
> > > >
> > > >
> > > > Regards.
> > > >
> > > >
> > > > rohit.ya...@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > > >
> > > > rohit.ya...@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > @shapeblue
> > >
> > >
> > >
> > >
>

Re: Release packages for 4.9.3.0

[Pierre-Luc Dion]

I've updated jenkins and built packages for centos6 and Ubuntu. Packages
have been copied on cloudstack.apt-get.eu automatically. I haven't tested
them yet.


Le 28 sept. 2017 20 h 19, "Pierre-Luc Dion"  a écrit :

I'll work something up this weekend...

we need some work on 4.10 I think...

On Thu, Sep 28, 2017 at 3:14 AM, Wido den Hollander  wrote:

>
> > Op 27 september 2017 om 8:30 schreef Özhan Rüzgar Karaman <
> oruzgarkara...@gmail.com>:
> >
> >
> > Hi Wido;
> > I checked http://cloudstack.apt-get.eu/ web site and 4.9.3 packages are
> > only under /ubuntu/dists/xenial/4.9/pool/ directory, for trusty there are
> > no packages available for 4.9.3 .
> >
> > This directory(/ubuntu/dists/xenial/4.9/pool/) also have 4.10 packages
> as
> > well, which i think they should not be there.
> >
> > When you have suitable time could you check the packages and its script.
> >
>
> Let me check that! Something must have gone wrong with the build and
> upload system. I'll check.
>
> Wido
>
> > Thanks
> > Özhan
> >
> > On Mon, Sep 25, 2017 at 7:24 AM, Rohit Yadav 
> > wrote:
> >
> > > Thanks Wido, can you help building and uploading of rpms as well. Maybe
> > > Pierre-Luc can help?
> > >
> > >
> > > - Rohit
> > >
> > > 
> > > From: Wido den Hollander 
> > > Sent: Thursday, September 21, 2017 1:09:49 PM
> > > To: Rohit Yadav; dev@cloudstack.apache.org; Pierre-Luc Dion
> > > Subject: Re: Release packages for 4.9.3.0
> > >
> > > Ah, sorry! The DEB packages should have been uploaded already :-)
> > >
> > > Wido
> > >
> > > > Op 21 september 2017 om 7:33 schreef Rohit Yadav <
> > > rohit.ya...@shapeblue.com>:
> > > >
> > > >
> > > > Ping - Wido/PL?
> > > >
> > > >
> > > > - Rohit
> > > >
> > > > 
> > > > From: Rohit Yadav 
> > > > Sent: Tuesday, September 12, 2017 5:44:36 PM
> > > > To: Wido den Hollander; Pierre-Luc Dion
> > > > Cc: dev@cloudstack.apache.org
> > > > Subject: Release packages for 4.9.3.0
> > > >
> > > > Wido/PL/others,
> > > >
> > > >
> > > > Can you please help with building and publishing of 4.9.3.0 rpms/deb
> > > packages on the download.cloudstack.org repository? I've built and
> > > published the repos on packages.shapeblue.com now (
> shapeblue.com/packages
> > > for details).
> > > >
> > > >
> > > > Regards.
> > > >
> > > >
> > > > rohit.ya...@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > 53 Chandos Place, Covent Garden, London  WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N&entry=gmail&source=g>
> 4HSUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > > >
> > > > rohit.ya...@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > 53 Chandos Place, Covent Garden, London  WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N&entry=gmail&source=g>
> 4HSUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N&entry=gmail&source=g>
> 4HSUK
> > > @shapeblue
> > >
> > >
> > >
> > >
>

Re: HTTPS LB and x-forwarded-for

[Pierre-Luc Dion]

Same challenge here too!

Let's look at improving Load-balancing offering from cloudstack, I guest we
should do a feature spec draft soon..,  from my perspective, doing SSL
offload on the VR could be problematic if the VR spec if too small, and the
default spec of the VR being 1vcpu@256MB, considering it can be the router
of a VPC, doing VPN termination, adding HTTPS  is a bit ish... What would
be your thought about this ?

I'd be curious to have a LB offering in ACS where it would deploy a
redundant traefik[1] beside the VR for doing http and https Load-balancing.
I think it would also be useful if the API of that traefik instance would
be available from within the VPC or LBnetwork so is API would be accessible
to other apps orchestration tools such as  kubernetes or rancher.

traefik or not, here is what I think is needed by cloudstack in the LB
improvement:

- support http, https (X-Forwarded-For)
- basic persistence tuning (API already exist)
- better backend monitoring, currently only a tcp connect validate if the
webserver is up.
- ssl offload
- metric collection, more stats, maybe just export the tool status page to
the private network.
- Container world support, right now if you have Rancher or kubernetes
cluster, you need to deploy your own LB solution behing mostlikely a static
nat., If cloudstack would deploy a traefik instance, Kub or Rancher could
reuse this instance and managed it to properly do LB between containers.


What would be your prefered LB tool:
haproxy, traefik or nginx?

CloudStack already have to code to handle SSL certs per projects and
accounts if not mistaking because that code was added to support NetScaler
as Load-balancer in the past. so one less thing to think about :-)


[1] https://traefik.io/


PL,



On Mon, Nov 6, 2017 at 7:10 AM, Nux!  wrote:

> Thanks Andrija,
>
> LB outside of the VR sounds like a good idea. An appliance based on, say
> cloud-init + ansible and so on could do the trick; alas it'd need to be
> outside ACS.
> I guess as users we could maybe come up with a spec for an improvement, at
> least we'd have something the devs could look at whenever it is possible.
>
> Regards,
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Andrija Panic" 
> > To: "dev" 
> > Cc: "users" 
> > Sent: Thursday, 2 November, 2017 23:21:37
> > Subject: Re: HTTPS LB and x-forwarded-for
>
> > We used to make some special stuff for one of the clients, where all LB
> > configuration work is done from outside of the ACS, i.e. python script to
> > feed/configure VR - install latest haproxy 1.5.x for transparent proxy,
> > since client insisted on SSL termination done on backend web SSL
> servers
> > Not good idea, that is all I can say (custom configuration thing) - but
> the
> > LB setup is actually good - transparent mode haproxy, works on TCP level,
> > so you can see "real client IP" on the backend servers (which must use VR
> > as the default gtw, as per default, so the whole setup works properly).
> >
> > I'm still looking forward to see some special support of LB inside VR via
> > ACS - proper LB setup inside VR via GUI/API -  i.e. to enable LB
> > provisioning SCRIPT (bash, or whatever),  where all needed
> > install+configure can be done from client side  - otherwise covering all
> > user cases, with proper HTTP checks and similaris impossible to do
> > IMHO.
> >
> > Some other clients, actually have internal FW appliance (i.e. multihomed
> > VM, acting as gtw for all VMs in all networks), and haproxy instaled on
> > this device (with NAT configured from VR to this internal FW/VM, so
> remote
> > IP can be seen properly) - this setup is fully under customer control,
> and
> > can provide any kind of special haproxy config...
> >
> >
> >
> >
> >
> >
> > On 31 October 2017 at 19:54, Nux!  wrote:
> >
> >> Hello,
> >>
> >> Of the people running an LB (VR) with https backends, how do you deal
> with
> >> the lack of x-forwarded-for since for port 443 there's just simple TCP
> >> balancing?
> >>
> >> Has anyone thought of terminating SSL in the VR instead? Ideas?
> >>
> >> Cheers
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>

Re: HTTPS LB and x-forwarded-for

[Pierre-Luc Dion]

I kind of like the proxy backend type, ill check on our end if that would
work but definitely a simple and efficient approach!



Le 10 nov. 2017 01 h 44, "Wido den Hollander"  a écrit :

>
> > Op 9 november 2017 om 19:59 schreef Nux! :
> >
> >
> > Wido,
> >
> > Excellent suggestion with the "transparent proxy", I was not aware of
> that.
> > I think that would be a great idea and wouldn't require too many
> modifications, especially as Haproxy comes already with the VR.
> >
>
> It's indeed just a matter of a HAProxy config setting. We could make it
> configurable per backend in HAProxy. Regular HTTP, TCP or PROXY for example.
>
> That way your problem would be solved.
>
> Wido
>
> > To Paul:
> > - imho the LB solution ACS ships now is a bit handicaped since you do
> not know the remote host ip. You're flying blind unless you use google
> analytics (and these things have gotten more and more aggressively filtered
> by adblocks).
> > Enhancing Haproxy as Wido suggested would go a long way, it wouldn't
> break existing functionality and would also keep SSL processing off the VR.
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> > > From: "Andrija Panic" 
> > > To: "users" 
> > > Cc: "Khosrow Moossavi" , "Will Stevens" <
> wstev...@cloudops.com>, "dev"
> > > , "Pierre-Luc Dion" 
> > > Sent: Thursday, 9 November, 2017 13:10:58
> > > Subject: Re: HTTPS LB and x-forwarded-for
> >
> > > Wido,
> > >
> > > backend servers are not Linux only, for example we have a ton of
> Windows
> > > customers, some WEB solutions / IIS etc...
> > >
> > > @all - If we try to please/solve everyone's proxying
> solution/requirement -
> > > this is impossible IMHO - I'm thinking more about some "do it as you
> like"
> > > solution, to let customer write his own haproxy config and upoad it
> (for
> > > example, or something better?).
> > >
> > > We can support newer version of haproxy (1.5+) which also implement
> > > "transarent proxy" (integrate with kernel so to speak)  to allow
> TCP-level
> > > connections to backend (TCP mode, not HTTP mode) but to still
> "preserve"
> > > remote IP by faking it (fake soruce IP = transarent proxy).
> > >
> > > For the rest of configuration options,  I would leave it to the
> customer
> > > how he/she wants to configure rest of haproxy configuration, inlcuding
> > > custom checks, etc. Haproxy configuration is never-ending story, and we
> > > probably should allow custom sripts/configuration instead of trying to
> > > provide GUI/API way to configure everything (which is impossible...)
> > >
> > > Just my 2 cents...
> > >
> > > On 9 November 2017 at 08:13, Wido den Hollander 
> wrote:
> > >
> > >>
> > >> > Op 8 november 2017 om 14:59 schreef Pierre-Luc Dion <
> pd...@cloudops.com
> > >> >:
> > >> >
> > >> >
> > >> > Same challenge here too!
> > >> >
> > >> > Let's look at improving Load-balancing offering from cloudstack, I
> guest
> > >> we
> > >> > should do a feature spec draft soon..,  from my perspective, doing
> SSL
> > >> > offload on the VR could be problematic if the VR spec if too small,
> and
> > >> the
> > >> > default spec of the VR being 1vcpu@256MB, considering it can be the
> > >> router
> > >> > of a VPC, doing VPN termination, adding HTTPS  is a bit ish... What
> would
> > >> > be your thought about this ?
> > >> >
> > >> > I'd be curious to have a LB offering in ACS where it would deploy a
> > >> > redundant traefik[1] beside the VR for doing http and https
> > >> Load-balancing.
> > >> > I think it would also be useful if the API of that traefik instance
> would
> > >> > be available from within the VPC or LBnetwork so is API would be
> > >> accessible
> > >> > to other apps orchestration tools such as  kubernetes or rancher.
> > >> >
> > >> > traefik or not, here is what I think is needed by cloudstack in the
> LB
> > >> > improvement:
> > >> >
> > &g

Re: HTTPS LB and x-forwarded-for

[Pierre-Luc Dion]

Hi Wido, do you know if this would work for https traffic too?

Le 10 nov. 2017 09 h 35, "Wido den Hollander"  a écrit :

>
> > Op 10 november 2017 om 14:27 schreef Pierre-Luc Dion  >:
> >
> >
> > I kind of like the proxy backend type, ill check on our end if that would
> > work but definitely a simple and efficient approach!
> >
>
> See: https://www.haproxy.com/blog/haproxy/proxy-protocol/
>
> Apache HTTPd supports PROXY since 2.4.28: https://httpd.apache.org/docs/
> trunk/mod/mod_remoteip.html#remoteipproxyprotocol
>
> "RemoteIPProxyProtocol is only available in httpd 2.4.28 and newer"
>
> Wido
>
> >
> >
> > Le 10 nov. 2017 01 h 44, "Wido den Hollander"  a écrit :
> >
> > >
> > > > Op 9 november 2017 om 19:59 schreef Nux! :
> > > >
> > > >
> > > > Wido,
> > > >
> > > > Excellent suggestion with the "transparent proxy", I was not aware of
> > > that.
> > > > I think that would be a great idea and wouldn't require too many
> > > modifications, especially as Haproxy comes already with the VR.
> > > >
> > >
> > > It's indeed just a matter of a HAProxy config setting. We could make it
> > > configurable per backend in HAProxy. Regular HTTP, TCP or PROXY for
> example.
> > >
> > > That way your problem would be solved.
> > >
> > > Wido
> > >
> > > > To Paul:
> > > > - imho the LB solution ACS ships now is a bit handicaped since you do
> > > not know the remote host ip. You're flying blind unless you use google
> > > analytics (and these things have gotten more and more aggressively
> filtered
> > > by adblocks).
> > > > Enhancing Haproxy as Wido suggested would go a long way, it wouldn't
> > > break existing functionality and would also keep SSL processing off
> the VR.
> > > >
> > > > --
> > > > Sent from the Delta quadrant using Borg technology!
> > > >
> > > > Nux!
> > > > www.nux.ro
> > > >
> > > > - Original Message -
> > > > > From: "Andrija Panic" 
> > > > > To: "users" 
> > > > > Cc: "Khosrow Moossavi" , "Will Stevens" <
> > > wstev...@cloudops.com>, "dev"
> > > > > , "Pierre-Luc Dion"  >
> > > > > Sent: Thursday, 9 November, 2017 13:10:58
> > > > > Subject: Re: HTTPS LB and x-forwarded-for
> > > >
> > > > > Wido,
> > > > >
> > > > > backend servers are not Linux only, for example we have a ton of
> > > Windows
> > > > > customers, some WEB solutions / IIS etc...
> > > > >
> > > > > @all - If we try to please/solve everyone's proxying
> > > solution/requirement -
> > > > > this is impossible IMHO - I'm thinking more about some "do it as
> you
> > > like"
> > > > > solution, to let customer write his own haproxy config and upoad it
> > > (for
> > > > > example, or something better?).
> > > > >
> > > > > We can support newer version of haproxy (1.5+) which also implement
> > > > > "transarent proxy" (integrate with kernel so to speak)  to allow
> > > TCP-level
> > > > > connections to backend (TCP mode, not HTTP mode) but to still
> > > "preserve"
> > > > > remote IP by faking it (fake soruce IP = transarent proxy).
> > > > >
> > > > > For the rest of configuration options,  I would leave it to the
> > > customer
> > > > > how he/she wants to configure rest of haproxy configuration,
> inlcuding
> > > > > custom checks, etc. Haproxy configuration is never-ending story,
> and we
> > > > > probably should allow custom sripts/configuration instead of
> trying to
> > > > > provide GUI/API way to configure everything (which is
> impossible...)
> > > > >
> > > > > Just my 2 cents...
> > > > >
> > > > > On 9 November 2017 at 08:13, Wido den Hollander 
> > > wrote:
> > > > >
> > > > >>
> > > > >> > Op 8 november 2017 om 14:59 schreef Pierre-Luc Dion <
> > > pd...@cloudops.com
> > > > >> >:
> > > > >> >
> > > > >

Re: HTTPS LB and x-forwarded-for

[Pierre-Luc Dion]

Hi,

This is looking quite promising, I have a colleague that tested that last
Friday, look like the proxy proto v1 work out of the box with Nginx, but
would need an extra package for Apache 2.4 ?
Otherwise, it seems to be a good way to do  https LB without complicated
configuration and huge changes in CloudStack.



On Fri, Nov 10, 2017 at 10:36 AM, Nux!  wrote:

> Pierre-Luc,
>
> Haproxy docs say it should work for any kind of traffic as long as both
> ends are PROXY-aware and it look like a majority of software is.
> So, in short, yes.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Pierre-Luc Dion" 
> > To: "Wido den Hollander" 
> > Cc: "dev" , "Khosrow Moossavi" <
> kmooss...@cloudops.com>, "Will Stevens"
> > , "Nux!" , "users" <
> us...@cloudstack.apache.org>
> > Sent: Friday, 10 November, 2017 15:32:38
> > Subject: Re: HTTPS LB and x-forwarded-for
>
> > Hi Wido, do you know if this would work for https traffic too?
> >
> > Le 10 nov. 2017 09 h 35, "Wido den Hollander"  a écrit :
> >
> >>
> >> > Op 10 november 2017 om 14:27 schreef Pierre-Luc Dion <
> pd...@cloudops.com
> >> >:
> >> >
> >> >
> >> > I kind of like the proxy backend type, ill check on our end if that
> would
> >> > work but definitely a simple and efficient approach!
> >> >
> >>
> >> See: https://www.haproxy.com/blog/haproxy/proxy-protocol/
> >>
> >> Apache HTTPd supports PROXY since 2.4.28:
> https://httpd.apache.org/docs/
> >> trunk/mod/mod_remoteip.html#remoteipproxyprotocol
> >>
> >> "RemoteIPProxyProtocol is only available in httpd 2.4.28 and newer"
> >>
> >> Wido
> >>
> >> >
> >> >
> >> > Le 10 nov. 2017 01 h 44, "Wido den Hollander"  a
> écrit :
> >> >
> >> > >
> >> > > > Op 9 november 2017 om 19:59 schreef Nux! :
> >> > > >
> >> > > >
> >> > > > Wido,
> >> > > >
> >> > > > Excellent suggestion with the "transparent proxy", I was not
> aware of
> >> > > that.
> >> > > > I think that would be a great idea and wouldn't require too many
> >> > > modifications, especially as Haproxy comes already with the VR.
> >> > > >
> >> > >
> >> > > It's indeed just a matter of a HAProxy config setting. We could
> make it
> >> > > configurable per backend in HAProxy. Regular HTTP, TCP or PROXY for
> >> example.
> >> > >
> >> > > That way your problem would be solved.
> >> > >
> >> > > Wido
> >> > >
> >> > > > To Paul:
> >> > > > - imho the LB solution ACS ships now is a bit handicaped since
> you do
> >> > > not know the remote host ip. You're flying blind unless you use
> google
> >> > > analytics (and these things have gotten more and more aggressively
> >> filtered
> >> > > by adblocks).
> >> > > > Enhancing Haproxy as Wido suggested would go a long way, it
> wouldn't
> >> > > break existing functionality and would also keep SSL processing off
> >> the VR.
> >> > > >
> >> > > > --
> >> > > > Sent from the Delta quadrant using Borg technology!
> >> > > >
> >> > > > Nux!
> >> > > > www.nux.ro
> >> > > >
> >> > > > - Original Message -
> >> > > > > From: "Andrija Panic" 
> >> > > > > To: "users" 
> >> > > > > Cc: "Khosrow Moossavi" , "Will
> Stevens" <
> >> > > wstev...@cloudops.com>, "dev"
> >> > > > > , "Pierre-Luc Dion" <
> pd...@cloudops.com
> >> >
> >> > > > > Sent: Thursday, 9 November, 2017 13:10:58
> >> > > > > Subject: Re: HTTPS LB and x-forwarded-for
> >> > > >
> >> > > > > Wido,
> >> > > > >
> >> > > > > backend servers are not Linux only, for example we have a ton of
> >> > > Windows
> >> > > > > customers, some WE

Re: HTTPS LB and x-forwarded-for

[Pierre-Luc Dion]

That's funny!

Cloudstack ui does not provide lb protocol options, but the api does and
cloudstack already support proxy proto v1!!!

So that's cool!

Le 13 nov. 2017 09 h 18, "Wido den Hollander"  a écrit :

>
> > Op 13 november 2017 om 15:14 schreef Pierre-Luc Dion  >:
> >
> >
> > Hi,
> >
> > This is looking quite promising, I have a colleague that tested that last
> > Friday, look like the proxy proto v1 work out of the box with Nginx, but
> > would need an extra package for Apache 2.4 ?
>
> It depends. You need HTTPd 2.4.28, see: https://httpd.apache.org/docs/
> trunk/mod/mod_remoteip.html#remoteipproxyprotocol
>
> It's there upstream, but not in all packages.
>
> It can from this module:
>
> - https://github.com/roadrunner2/mod-proxy-protocol
> - https://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html
>
> They donated the code to go upstream and went into mod_remoteip but landed
> in 2.4.28
>
> It will probably make it into Ubuntu 18.04 and CentOS 7.4.
>
> Wido
>
> > Otherwise, it seems to be a good way to do  https LB without complicated
> > configuration and huge changes in CloudStack.
> >
> >
> >
> > On Fri, Nov 10, 2017 at 10:36 AM, Nux!  wrote:
> >
> > > Pierre-Luc,
> > >
> > > Haproxy docs say it should work for any kind of traffic as long as both
> > > ends are PROXY-aware and it look like a majority of software is.
> > > So, in short, yes.
> > >
> > > --
> > > Sent from the Delta quadrant using Borg technology!
> > >
> > > Nux!
> > > www.nux.ro
> > >
> > > - Original Message -
> > > > From: "Pierre-Luc Dion" 
> > > > To: "Wido den Hollander" 
> > > > Cc: "dev" , "Khosrow Moossavi" <
> > > kmooss...@cloudops.com>, "Will Stevens"
> > > > , "Nux!" , "users" <
> > > us...@cloudstack.apache.org>
> > > > Sent: Friday, 10 November, 2017 15:32:38
> > > > Subject: Re: HTTPS LB and x-forwarded-for
> > >
> > > > Hi Wido, do you know if this would work for https traffic too?
> > > >
> > > > Le 10 nov. 2017 09 h 35, "Wido den Hollander"  a
> écrit :
> > > >
> > > >>
> > > >> > Op 10 november 2017 om 14:27 schreef Pierre-Luc Dion <
> > > pd...@cloudops.com
> > > >> >:
> > > >> >
> > > >> >
> > > >> > I kind of like the proxy backend type, ill check on our end if
> that
> > > would
> > > >> > work but definitely a simple and efficient approach!
> > > >> >
> > > >>
> > > >> See: https://www.haproxy.com/blog/haproxy/proxy-protocol/
> > > >>
> > > >> Apache HTTPd supports PROXY since 2.4.28:
> > > https://httpd.apache.org/docs/
> > > >> trunk/mod/mod_remoteip.html#remoteipproxyprotocol
> > > >>
> > > >> "RemoteIPProxyProtocol is only available in httpd 2.4.28 and newer"
> > > >>
> > > >> Wido
> > > >>
> > > >> >
> > > >> >
> > > >> > Le 10 nov. 2017 01 h 44, "Wido den Hollander"  a
> > > écrit :
> > > >> >
> > > >> > >
> > > >> > > > Op 9 november 2017 om 19:59 schreef Nux! :
> > > >> > > >
> > > >> > > >
> > > >> > > > Wido,
> > > >> > > >
> > > >> > > > Excellent suggestion with the "transparent proxy", I was not
> > > aware of
> > > >> > > that.
> > > >> > > > I think that would be a great idea and wouldn't require too
> many
> > > >> > > modifications, especially as Haproxy comes already with the VR.
> > > >> > > >
> > > >> > >
> > > >> > > It's indeed just a matter of a HAProxy config setting. We could
> > > make it
> > > >> > > configurable per backend in HAProxy. Regular HTTP, TCP or PROXY
> for
> > > >> example.
> > > >> > >
> > > >> > > That way your problem would be solved.
> > > >> > >
> > > >> > > Wido
> > > >> > >
> > > >> > > > 

Re: Fail with vpn customer gateway creation through terraform

[Pierre-Luc Dion]

Hi Nux,

Could it be your cloudstack version ?  modp3072 is recent I think in
CloudStack so if you run a older version maybe it's not there?



On Tue, Nov 21, 2017 at 6:55 PM, Nux!  wrote:

> Thanks Chiradeep,
>
> Checked but brain says no. What should I have learned from there?
>
> AFAIK this is a terraform fail.
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Chiradeep Vittal" 
> > To: "dev" 
> > Sent: Tuesday, 21 November, 2017 19:14:16
> > Subject: Re: Fail with vpn customer gateway creation through terraform
>
> > Check
> > https://github.com/apache/cloudstack/blob/77864992fe8f80dbabd1240f6373d2
> ba3e98713c/utils/src/main/java/com/cloud/utils/net/NetUtils.java#L1221
> >
> > On Tue, Nov 21, 2017 at 10:11 AM, Nux!  wrote:
> >
> >> Hi,
> >>
> >> I'm trying out terraform and had success so far, except for the vpn
> >> customer gateway feature.
> >> For some reason, terraform fails to create it, though I use the same
> >> options as in UI/cloudmonkey where it works just fine.
> >>
> >> The snippet for it is:
> >>
> >> resource "cloudstack_vpn_customer_gateway" "default" {
> >>   name   = "test-vpc"
> >>   cidr   = "10.0.0.0/24"
> >>   esp_policy = "aes256-sha1"
> >>   gateway= "1.2.3.4"
> >>   ike_policy = "sha1-aes256;modp3072"
> >>   ipsec_psk  = "terraformxyz7"
> >> }
> >>
> >> It always complains about the ike_policy:
> >> * cloudstack_vpn_customer_gateway.default: Error creating VPN Customer
> >> Gateway test-vpc: Undefined error: {"errorcode":431,"errortext":"The
> >> customer gateway IKE policy sha1-aes256;modp3072 is invalid!  Verify the
> >> required Diffie Hellman (DH) group is specified."}
> >>
> >> I tried all sorts of ways to write the ike_policy, escaped, web
> >> encoded/decoded, nothing worked. What am I missing?
> >> The example terraform docs provide suffers the same fate.
> >>
> >> Lucian
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
>

[VR] dnsmasq reload instead of restart

[Pierre-Luc Dion]

Hi,

We recently found a way to reload dnsmasq process instead of doing a
restart.
Does anyone see a problem with that?  Basically we have to change where the
file /etc/dhcphosts.txt is define in the config so it would be define via
"--dhcp-hostsfile=/etc/dhcphosts.txt" when the process is start so it would
be re-read in a kill -HUP.

The problem to solve here is that during VM.CREATE in a VPC, the dns
service is restarted and cause DNS service interruption to VM inside the
VPC.

We are preparing a PR for this.

is this could be problematic for rVR ?

Thanks,

PL

Re: [VR] dnsmasq reload instead of restart

[Pierre-Luc Dion]

good point !

Based on what I understand from dnsmasq, reload will not update conf for
the interface of a new network tier.



On Fri, Nov 24, 2017 at 6:44 PM, Erik Weber  wrote:

> I'm not sure if this applies to dnsmasq or not, but some services does
> not bind to new interfaces during a reload.
> Meaning you'll have to be sure the reason you're reloading isn't
> because of something that added a device (say adding a new tier or
> similar).
>
> --
> Erik
>
> On Fri, Nov 24, 2017 at 9:05 PM, Pierre-Luc Dion 
> wrote:
> > Hi,
> >
> > We recently found a way to reload dnsmasq process instead of doing a
> > restart.
> > Does anyone see a problem with that?  Basically we have to change where
> the
> > file /etc/dhcphosts.txt is define in the config so it would be define via
> > "--dhcp-hostsfile=/etc/dhcphosts.txt" when the process is start so it
> would
> > be re-read in a kill -HUP.
> >
> > The problem to solve here is that during VM.CREATE in a VPC, the dns
> > service is restarted and cause DNS service interruption to VM inside the
> > VPC.
> >
> > We are preparing a PR for this.
> >
> > is this could be problematic for rVR ?
> >
> > Thanks,
> >
> > PL
>

Re: Release Notes

[Pierre-Luc Dion]

The way I was doing RN and generating  fixed issues and known issues list,
was by doing JIRA filters for each of them, then you use "./utils/jira.py"
from cloudstack-docs-rn
to generate a markdown formated list that you cut/paste in relevant RN
page.  This require Jira issues to be updated on Open/close  state, also
the Fix Version and Affected to be fully up to date. With recent use of
Gitbhub, I'm not sure how Jira is up to date now.  Will did use something
else to extract data from commit comments, but I don't know how he did it.

Hope this help a little...


Cheers,




On Thu, Dec 21, 2017 at 12:38 PM, Paul Angus 
wrote:

>
> Hi guys I'm hoping to get a head start on release notes over Xmas. I
> believe some guys have come up with a tool which gets human readable what's
> new and known issues...
>
> Could someone point me in the right direction please.
>
> (And merry Christmas and a happy new year to everyone)
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: Performance considerations related to Intel Meltdown on KVM CPU types

[Pierre-Luc Dion]

Thanks for sharing this Nux!

PL

On Mon, Jan 8, 2018 at 10:11 AM, Nux!  wrote:

> Hello,
>
> Just stumbled upon this
> https://twitter.com/berrange/status/950209752486817792
>
> "ensure KVM guest CPU model you choose has the "pcid" feature, otherwise
> guests will suffer terrible performance from the Meltdown fixes. This means
> using a named Haswell, Broadwell or Skylake based model or host passthrough"
>
>
> This means whoever is running with the KVM default CPU (like I do) as
> opposed to specific ones or host passthrough needs to change this in order
> to avoid bad performance once the new mitigating kernel is installed.
>
>
> Bad news is older Xeons do not support this, check if "invpcid" flag shows
> up in /proc/cpuinfo (you might see "pcid", that one is not enough).
>
>
>
>
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>

[XenServer] meltdown-spectre

[Pierre-Luc Dion]

 Hi,

>From recent blog post, I've read that system using full virtualization such
as KVM, VMware or Xen-HVM are not affected?  Anyhow, from the latest hotfix
of XenServer 7.1cu1 hf8, it look like they systematically convert VM from
PV to HVM, so in the case of a VM stop/start by CloudStack, a PV vm would
be restarted as HVM.

Look like this could be problematic if your VM kernel does not support
both, we've just starting tested and so far look like our Debian systemvm
template work fine, it can be created as HVM.

Another point is that Citrix released an hotfix for xs7.2, 7.3 but not for
7.1, you need to cumulative update to remain on 7.1 which is LTS.

And last, does anyone did some benchmark before and after the kernel fix
for Meltdown ?  Some report state 30-35% cpu usage increase (not hypervisor
specific) and  Lucian [1] might indicate it would depend on the cpu model.
Any metrics to share ?  We are doing some tests on our side we should be
able to share some stuff soon...

Regards,

[1] http://markmail.org/thread/wkzze3n24mns274x

Re: [XenServer] meltdown-spectre

[Pierre-Luc Dion]

Hi,

Another problem,  VR are configured via eth0 (cloudlinklocal) that is
create via PV params of the VM on XenServer. So Creation HVM VR will not
work. We will have to think about an alternative way to setup eth0 on VR on
XenServer.
We will file a jira issue about this. This will be problematic with XS
7,1cu1, 7.2, 7.3

Tim, yes fro XS template, the maping, at least on Xs7.1 seams to work just
fine. They were pretty much all as HVM exept Centos 6, Debian,.. until the
Meltdown hotfix.




On Mon, Jan 8, 2018 at 10:47 PM, Tim Mackey  wrote:

> PLD,
>
> One thing to add to your testing is template management. When I was doing
> all the Packer stuff with XS 6.5 and 7, ACS needed to know if the template
> was PV or HVM to provision properly. No idea if the ACS template logic has
> changed since then, but something to be aware of.
>
> From a performance perspective with XS 6.5 started having newer XS
> templates follow an HVM model. e.g. CentOS 7 on XS 6.5 was HVM not PV.
> iirc, the performance difference was negligible on reasonably new CPUs
> (Sandy Bridge+ I think).
>
> -tim
>
> On Mon, Jan 8, 2018 at 9:39 PM, Ivan Kudryavtsev  >
> wrote:
>
> > Hi. Every kind of virtualization is affected according to qemu
> developers.
> >
> > 9 янв. 2018 г. 9:32 пользователь "Pierre-Luc Dion" 
> > написал:
> >
> > >  Hi,
> > >
> > > From recent blog post, I've read that system using full virtualization
> > such
> > > as KVM, VMware or Xen-HVM are not affected?  Anyhow, from the latest
> > hotfix
> > > of XenServer 7.1cu1 hf8, it look like they systematically convert VM
> from
> > > PV to HVM, so in the case of a VM stop/start by CloudStack, a PV vm
> would
> > > be restarted as HVM.
> > >
> > > Look like this could be problematic if your VM kernel does not support
> > > both, we've just starting tested and so far look like our Debian
> systemvm
> > > template work fine, it can be created as HVM.
> > >
> > > Another point is that Citrix released an hotfix for xs7.2, 7.3 but not
> > for
> > > 7.1, you need to cumulative update to remain on 7.1 which is LTS.
> > >
> > > And last, does anyone did some benchmark before and after the kernel
> fix
> > > for Meltdown ?  Some report state 30-35% cpu usage increase (not
> > hypervisor
> > > specific) and  Lucian [1] might indicate it would depend on the cpu
> > model.
> > > Any metrics to share ?  We are doing some tests on our side we should
> be
> > > able to share some stuff soon...
> > >
> > > Regards,
> > >
> > > [1] http://markmail.org/thread/wkzze3n24mns274x
> > >
> >
>

Re: [PROPOSE] EOL for supported OSes & Hypervisors

[Pierre-Luc Dion]

+1!

Do you think it would be the right page to also have debian version used by
the ssvm?

For the management-server section the cloudstack column would list the last
acs version tested on that OS?


Le 11 janv. 2018 12 h 53, "Will Stevens"  a écrit :

> I like this initiative.  I think this would be valuable to set an
> expectation around supportability.
>
> Cheers,
>
> *Will Stevens*
> CTO
>
> 
>
> On Thu, Jan 11, 2018 at 12:11 PM, Paul Angus 
> wrote:
>
> > I've cross-posted this as it ultimately effects users more than
> developers.
> >
> > I've created a wiki page with the EOL dates from the respective 'vendors'
> > of our main supported hypervisors and mgmt. server OSes.
> > I've taken End Of Life to be the end of 'mainstream' support i.e. the
> > point at which updates to packages will no longer be available.  And part
> > of the discussion should be whether this EOL date should be moved out to
> > consider end of security patching instead.
> >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> > WIP+-+UNOFFICIAL+-+PROPOSAL+-+EOL+Dates
> >
> > I would like to propose, that as part of the release notes for the
> > forthcoming 4.11 release and as a general announcement, that we declare
> > that:
> >
> >
> >   *   For any OSes/Hypervisors that are already EOL - we will no longer
> > test/support them from the first release after June 2018 (6 months from
> > now). And they will be removed from codebase (mainly the database) in the
> > first release after Sept 2018 (9 months from now).
> >   *   We set End Of Support dates and Removal from Code dates for the
> > remaining OSes/Hypervisors.  I propose that End Of Support should be the
> > first release after EOL from the vendor, with code removal taking place
> in
> > the first release which occurs after 6 months from 'vendor' EOL date.
> >
> > Thoughts please
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>

[DISCUSS] running sVM and VR as HVM on XenServer

[Pierre-Luc Dion]

Hi,

We need to start a architecture discussion about running SystemVM and
Virtual-Router as HVM instances in XenServer. With recent Meltdown-Spectre,
one of the mitigation step is currently to run VMs as HVM on XenServer to
self contain a user space attack from a guest OS.

Recent hotfix from Citrix XenServer (XS71ECU1009) enforce VMs to start has
HVM. This is currently problematic for Virtual Routers and SystemVM because
CloudStack use PV "OS boot Options" to preconfigure the VR eth0:
cloud_link_local. While using HVM the "OS boot Options" is not accessible
to the VM so the VR fail to be properly configured.

I currently see 2 potential approaches for this:
1. Run a dhcpserver in dom0 managed by cloudstack so VR eth0 would receive
is network configuration at boot.
2. Change the current way of managing VR, SVMs on XenServer, potentiall do
same has with VMware: use pod management networks and assign a POD IP to
each VR.

I don't know how it's implemented in KVM, maybe cloning KVM approach would
work too, could someone explain how it work on this thread?

I'd a bit fan of a potential #2 aproach because it could facilitate VR
monitoring and logging, although a migration path for an existing cloud
could be complex.

Cheers,


Pierre-Luc

Re: [DISCUSS] running sVM and VR as HVM on XenServer

[Pierre-Luc Dion]

After some verification with Syed and Khosrow,

We found that we can use xenstore-read / xenstore-write to send data from
dom0 to domU which are in our case  VRs or SVMs. Any reason not using this
approach ?  that way we would not need a architectural change for XenServer
pods, and this would support HVM and PV virtual-router. more test required,
for sure, VR would need to have xentools pre-installed.


*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jan 12, 2018 at 4:07 PM, Syed Ahmed  wrote:

> KVM uses a VirtIO channel to send information about the IP address and
> other params to the SystemVMs. We could use a similar strategy in XenServer
> using XenStore. This would involve minimal changes to the code while
> keeping backward compatibility.
>
>
>
> On Fri, Jan 12, 2018 at 3:07 PM, Simon Weller 
> wrote:
>
> > They do not. They receive a link-local ip address that is used for host
> > agent to VR communication. All VR commands are proxied through the host
> > agent. Host agent to VR communication is over SSH.
> >
> >
> > 
> > From: Rafael Weingärtner 
> > Sent: Friday, January 12, 2018 1:42 PM
> > To: dev
> > Subject: Re: [DISCUSS] running sVM and VR as HVM on XenServer
> >
> > but we are already using this design in vmware deployments (not sure
> about
> > KVM). The management network is already an isolated network only used by
> > system vms and ACS. Unless we are attacked by some internal agent, we are
> > safe from customer attack through management networks. Also, we can (if
> we
> > don't do yet) restrict access only via these management interfaces in
> > system VMs(VRs, SSVM, console proxy and others to come).
> >
> >
> >
> > Can someone confirm if VRs receive management IPs in KVM deployments?
> >
> > On Fri, Jan 12, 2018 at 5:36 PM, Syed Ahmed  wrote:
> >
> > > The reason why we used link local in the first place was to isolate the
> > VR
> > > from directly accessing the management network. This provides another
> > layer
> > > of security in case of a VR exploit. This will also have a side effect
> of
> > > making all VRs visible to each other. Are we okay accepting this?
> > >
> > > Thanks,
> > > -Syed
> > >
> > > On Fri, Jan 12, 2018 at 11:37 AM, Tim Mackey 
> wrote:
> > >
> > > > dom0 already has a DHCP server listening for requests on internal
> > > > management networks. I'd be wary trying to manage it from an external
> > > > service like cloudstack lest it get reset upon XenServer patch. This
> > > alone
> > > > makes me favor option #2. I also think option #2 simplifies network
> > > design
> > > > for users.
> > > >
> > > > Agreed on making this as consistent across flows as possible.
> > > >
> > > >
> > > >
> > > > On Fri, Jan 12, 2018 at 9:44 AM, Rafael Weingärtner <
> > > > rafaelweingart...@gmail.com> wrote:
> > > >
> > > > > It looks reasonable to manage VRs via management IP network. We
> > should
> > > > > focus on using the same work flow for different deployment
> scenarios.
> > > > >
> > > > >
> > > > > On Fri, Jan 12, 2018 at 12:13 PM, Pierre-Luc Dion <
> > pd...@cloudops.com>
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > We need to start a architecture discussion about running SystemVM
> > and
> > > > > > Virtual-Router as HVM instances in XenServer. With recent
> > > > > Meltdown-Spectre,
> > > > > > one of the mitigation step is currently to run VMs as HVM on
> > > XenServer
> > > > to
> > > > > > self contain a user space attack from a guest OS.
> > > > > >
> > > > > > Recent hotfix from Citrix XenServer (XS71ECU1009) enforce VMs to
> > > start
> > > > > has
> > > > > > HVM. This is currently problematic for Virtual Routers and
> SystemVM
> > > > > because
> > > > > > CloudStack use PV "OS boot Options" to preconfigure the VR eth0:
> > > > > > cloud_link_local. While using HVM the "OS boot Options" is not
> > > &

Re: [DISCUSS] running sVM and VR as HVM on XenServer

[Pierre-Luc Dion]

Hi Tim,

As long as it work, since it's only used to for the initial instruction set
at the VR boot so eth0 can be configure, I think xenstore would work just
fine.
unless you are saying we could just not rely on xenstore in terms of
reliability?


*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jan 12, 2018 at 7:34 PM, Tim Mackey  wrote:

> > We found that we can use xenstore-read / xenstore-write to send data from
> dom0 to domU which are in our case  VRs or SVMs. Any reason not using this
> approach ?
>
> xenstore has had some issues in the past. The most notable of which were
> limitations on the number of event channels in use, followed by overall
> performance impact. iirc, the event channel stuff was fully resolved with
> XenServer 6.5, but they do speak to a need to test if there are any changes
> to the maximum number of VMs which can be reliably supported. It also
> limits legacy support (in case that matters).
>
> Architecturally I think this is a reasonable approach to the problem. One
> other thing to note is that xapi replicates xenstore information to all
> members of a pool. That might impact RVRs.
>
> -tim
>
> [1] "xenstore is not a high-performance facility and should beused only for
> small amounts of control plane data."
> https://xenbits.xen.org/docs/4.6-testing/misc/xenstore.txt
>
> On Fri, Jan 12, 2018 at 4:56 PM, Pierre-Luc Dion 
> wrote:
>
> > After some verification with Syed and Khosrow,
> >
> > We found that we can use xenstore-read / xenstore-write to send data from
> > dom0 to domU which are in our case  VRs or SVMs. Any reason not using
> this
> > approach ?  that way we would not need a architectural change for
> XenServer
> > pods, and this would support HVM and PV virtual-router. more test
> required,
> > for sure, VR would need to have xentools pre-installed.
> >
> >
> > *Pierre-Luc DION*
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > t 855.652.5683
> >
> > *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Fri, Jan 12, 2018 at 4:07 PM, Syed Ahmed  wrote:
> >
> > > KVM uses a VirtIO channel to send information about the IP address and
> > > other params to the SystemVMs. We could use a similar strategy in
> > XenServer
> > > using XenStore. This would involve minimal changes to the code while
> > > keeping backward compatibility.
> > >
> > >
> > >
> > > On Fri, Jan 12, 2018 at 3:07 PM, Simon Weller  >
> > > wrote:
> > >
> > > > They do not. They receive a link-local ip address that is used for
> host
> > > > agent to VR communication. All VR commands are proxied through the
> host
> > > > agent. Host agent to VR communication is over SSH.
> > > >
> > > >
> > > > 
> > > > From: Rafael Weingärtner 
> > > > Sent: Friday, January 12, 2018 1:42 PM
> > > > To: dev
> > > > Subject: Re: [DISCUSS] running sVM and VR as HVM on XenServer
> > > >
> > > > but we are already using this design in vmware deployments (not sure
> > > about
> > > > KVM). The management network is already an isolated network only used
> > by
> > > > system vms and ACS. Unless we are attacked by some internal agent, we
> > are
> > > > safe from customer attack through management networks. Also, we can
> (if
> > > we
> > > > don't do yet) restrict access only via these management interfaces in
> > > > system VMs(VRs, SSVM, console proxy and others to come).
> > > >
> > > >
> > > >
> > > > Can someone confirm if VRs receive management IPs in KVM deployments?
> > > >
> > > > On Fri, Jan 12, 2018 at 5:36 PM, Syed Ahmed 
> > wrote:
> > > >
> > > > > The reason why we used link local in the first place was to isolate
> > the
> > > > VR
> > > > > from directly accessing the management network. This provides
> another
> > > > layer
> > > > > of security in case of a VR exploit. This will also have a side
> > effect
> > > of
> > > > > making all VRs visible to each other. Are we okay accepting th

Re: Copy Volume Failed in CloudStack 4.5 (XenServer 6.5)

[Pierre-Luc Dion]

I think there is a timout global settings you could change so the copy task
will take longer before it timeout and fail in cloudstack. This will not
improve your performance but might reduce failure.

On updating the database content, it could work, but only if the vhd
successfully copy, and mappings remain valid.

I hope this can help...



Le 6 févr. 2018 13 h 28, "anillakieni"  a
écrit :

Dear All,

Is somebody available here to assist me on fixing my issue.

Thanks,
Anil.

On Tue, Feb 6, 2018 at 9:00 PM, anillakieni  wrote:

> Hi All,
>
> I'm facing issue when copying  larger size volumes. i.e., Secondary
> Storage to Primary Storage (I mean attaching DATA volume to VM), after
> certain time around 37670 seconds.
>
> Version of:
> - CloudStack is 4.5.0
> - XenServer 6.5.0
> - MySQL 5.1.73
>
>
> The error and log is provided below, Could someone please assist me here
> which steps i have to take to fix this issue. Also, can we have a chance
to
> update the failed status to success through database tables because i have
> to upload the whole disk again to secondary storage and then later attach
> it to VM, which is consuming more time. My environment has very slow
> network transfers (I have only 1 Gig switch). Please let me know if we can
> tweak the DB to update the status of the disk or do we have any settings
to
> be changed to accept more time (wait time) for updating the status.
> "
>
> 2018-02-06 03:20:42,385 DEBUG [c.c.a.t.Request] (Work-Job-Executor-31:ctx-
c1c78a5a
> job-106186/job-106187 ctx-ea1ef3e6) (logid:c59b2359) Seq
> 38-367887794560851961: Received:  { Ans: , MgmtId: 47019105324719, via:
38,
> Ver: v1, Flags: 110, { CopyCmdAnswer } }
> 2018-02-06 03:20:42,389 DEBUG [o.a.c.s.v.VolumeObject]
> (Work-Job-Executor-31:ctx-c1c78a5a job-106186/job-106187 ctx-ea1ef3e6)
> (logid:c59b2359) *Failed to update state*
> *com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
> com.mysql.jdbc.JDBC4PreparedStatement@54bd3a25: SELECT volume_store_ref.id
> , volume_store_ref.store_id,
> volume_store_ref.volume_id, volume_store_ref.zone_id,
> volume_store_ref.created, volume_store_ref.last_updated,
> volume_store_ref.download_pct, volume_store_ref.size,
> volume_store_ref.physical_size, volume_store_ref.download_state,
> volume_store_ref.checksum, volume_store_ref.local_path,
> volume_store_ref.error_str, volume_store_ref.job_id,
> volume_store_ref.install_path, volume_store_ref.url,
> volume_store_ref.download_url, volume_store_ref.download_url_created,
> volume_store_ref.destroyed, volume_store_ref.update_count,
> volume_store_ref.updated, volume_store_ref.state, volume_store_ref.ref_cnt
> FROM volume_store_ref WHERE volume_store_ref.store_id = 1  AND
> volume_store_ref.volume_id = 1178  AND volume_store_ref.destroyed = 0
> ORDER BY RAND() LIMIT 1*
> at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(
> GenericDaoBase.java:425)
> at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(
> GenericDaoBase.java:361)
> at com.cloud.utils.db.GenericDaoBase.findOneIncludingRemovedBy(
> GenericDaoBase.java:889)
> at com.cloud.utils.db.GenericDaoBase.findOneBy(
> GenericDaoBase.java:900)
> at org.apache.cloudstack.storage.image.db.VolumeDataStoreDaoImpl.
> findByStoreVolume(VolumeDataStoreDaoImpl.java:209)
> at sun.reflect.GeneratedMethodAccessor306.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:317)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> TransactionContextInterceptor.java:34)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:161)
> at org.springframework.aop.interceptor.
> ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> at org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy173.findByStoreVolume(Unknown Source)
> at org.apache.cloudstack.storage.datastore.
> ObjectInDataStoreManagerImpl.findObject(ObjectInDataStoreManagerImpl.
> java:353)
> at org.apache.cloudstack.storage.datastore.
> ObjectInDataStoreManagerImpl.findObject(ObjectInDataStoreManagerImpl.
> java:338)
> at org.apache.cloudstack.storage.datastore.
> ObjectInDataStoreManagerImpl.update(ObjectInDataStoreManagerIm

I'd like to introduce you to Khosrow

[Pierre-Luc Dion]

Hi fellow colleagues,

I might be a bit late with this email...

I'd like to introduce Khosrow Moossavi, who recently join our team and his
focus is currently exclusively on dev for Cloudstack with cloud.ca.

Our 2 current priorities are:
-fixing VRs,SVMs to run has HVM VMs in xenserver.
- redesign, or rewrite, the remote management vpn for vpc, poc in progress
for IKEv2...



Some of you might have interact with him already.


Also, we are going to be more active for the upcomming 4.12 release.


Cheers!

Re: Infra Shutdown (Jenkins?)

[Pierre-Luc Dion]

Hi Rohit, Will,

I have a backup of the jenkins.xml but it's from a while back, it
shouldn't  have changed much since recent work was done on
builds.cloudstack.org and github if not mistaking.
We also provide an alternative: https://builds.cloudstack.org/ hosted on
cloud.ca



On Wed, Jun 27, 2018 at 11:35 AM Rohit Yadav 
wrote:

> Will, you may take the xml jenkings config backup of the jenkins box if
> possible.
>
> Regards.
>
> Get Outlook for Android
>
> 
> From: Will Stevens 
> Sent: Wednesday, June 27, 2018 7:38:48 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Infra Shutdown (Jenkins?)
>
> Hey All,
> I am guessing since I have not heard anyone scream that this infra was not
> used.  I will be blowing these resources away by the end of the week if no
> one is using these resources.
>
> Cheers,
>
> *Will Stevens*
> Chief Technology Officer
> c 514.826.0190
>
> 
>
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> On Fri, Jun 22, 2018 at 8:40 AM Will Stevens 
> wrote:
>
> > Hey Everyone,
> > So CloudOps took over paying for a Citrix AWS account a couple years ago
> > which apparently has VMs which is supporting the ACS community.  This
> > account has been costing us about $500/month, so we want to make sure the
> > VMs are actually used.
> >
> > I am shutting down the following VMs and if things stop working, please
> > let me know...
> >
> > - jenkins.cloudstack.org | IP: 75.101.146.23 | KeyPair: davidnalley
> > - deb build large | IP: 54.242.16.44 | KeyPair: edison
> > -  | IP: 54.90.178.215 | KeyPair: davidnalley
> > - PEOPLE AND FPASTE | IP: 107.21.237.59 | KeyPair: davidnalley
> >
> > If any of these VMs mean anything to you, please reach out to me.  I
> can't
> > justify paying for them if I don't know they are used.
> >
> > Thanks,
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > 
> >
>

[DISCUSS] deployment planner improvement

[Pierre-Luc Dion]

Hi,

I'm working with a University in Montreal and we are looking at working
together to improve the deployment planner. Mainly for post VM.CREATE tasks.
Because  what we observed with cloudstack, in our case with XenServer,
overtime, a cluster will become unbalanced in therm of workload, vm HA will
move VMs all over the the cluster which cause hotspot inside a cluster.
Also, when performing maintenance  xenmotion of VM spread them in the
cluster but does not consider host usage and at the end of a maintenance it
require manual operation to repopulate VMs on the last host updated.  OS
preference not taken into account  except for VM.CREATE.

So,
I'd like to work on improving VMs dispersion during and post outage and
maintenances. when a cluster resources are added or removed.

Would you have any more requirement, we will document a feature spec in the
wiki which I believe it's still a requirement ?

Does using KVM have similar issues over time?

I don't think it would make sense to cloudstack to automatically take
decision on moving VMs but for now create report of recommended action to
do and provide steps to do them. tbd.

Cheers,

PL

Re: [DISCUSS] Removing IAM services

[Pierre-Luc Dion]

No chances it's in used with Roles stuff ?




On Wed, Aug 22, 2018 at 8:19 AM Gabriel Beims Bräscher 
wrote:

> I am +1 on removing it as well.
>
> Em qua, 22 de ago de 2018 às 07:49, Rohit Yadav  >
> escreveu:
>
> > +1 it's about time
> >
> >
> >
> > - Rohit
> >
> > 
> >
> >
> >
> > 
> > From: Daan Hoogland 
> > Sent: Tuesday, August 21, 2018 9:02:58 PM
> > To: dev
> > Cc: users
> > Subject: [DISCUSS] Removing IAM services
> >
> > i'm +1 on this it has not been developed for the longest while. (changed
> > the title to indicate _all_ people are supposed to have an opinion.)
> >
> > On Tue, Aug 21, 2018 at 4:32 PM, Khosrow Moossavi <
> kmooss...@cloudops.com>
> > wrote:
> >
> > > Hello Community
> > >
> > > Following up after PR#2613[1] to cleanup POMs across the whole
> > repository,
> > > now in a new
> > > PR #2817 we are going to remove services/iam projects which seems to be
> > > disabled and
> > > not maintained since May 2014.
> > >
> > > Moving forward with the PR, corresponding tables will be deleted from
> > > database too.
> > >
> > > Please let us know if you have any questions, comments, concerns about
> > this
> > > removal or if
> > > you are willing to revive the project in some shape or form.
> > >
> > > [1]: https://github.com/apache/cloudstack/pull/2613
> > > [2]: https://github.com/apache/cloudstack/pull/2817
> > >
> > > Khosrow Moossavi
> > >
> > > Cloud Infrastructure Developer
> > >
> > > 
> > >
> >
> >
> >
> > --
> > Daan
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>

Re: [DISCUSS] deployment planner improvement

[Pierre-Luc Dion]

#scopecreep Paul ;)

But I think the problem you identify is related to selection of the
deployment planner strategy, globally define or at the compute offering.
You can select how cloudstack choose the host to deploy a new vm.

But even then, like marcus stated, if you add a node to a full cluster, all
new vm will be created on that node.

So if nobody have WIP around post deployment orchestration, I'll work on
the feature spec with the university, with objective in mind to easy
hypervisor maintenances, better distribution of workload.

I would not expect PR before ~6months, but will have some actions around it
very soon I hope.



Le ven. 7 sept. 2018 09 h 05, Marc-Andre Jutras  a
écrit :

> I agree, it is affecting all hypervisor... I basically had to migrate a
> bunch of vm manually to re-balance a cluster after an upgrade or even
> after re-adding new host to a cluster.
>
> Personally, I think Cloudstack should be able to handles this  balancing> of resource, example: having a piece of code somewhere that
> can run every hours or on demand to re-calculate and re-balance
> resources across hosts within a cluster...
>
> Even the deployment planner is not really relevant here: this process
> will basically balance new VM creation through different clusters of a
> POD, not between hosts within a cluster and it's also becoming a
> nightmare when you start to do cross-cluster migration...
>
> Sum of all : The deployment strategies planner should be re-worked a bit...
>
> +1 on #scoopcreep ;)
>
> Marcus ( mjut...@cloudops.com )
>
> On 2018-09-07 6:01 AM, Paul Angus wrote:
> > I think that this affects all hypervisors as CloudStack's deployment
> strategies are generally sub-optimal to say the least.
> >  From what our devs have told me, a large part of the problem is that
> capacity/usage and suitability due to tags is calculated by multiple parts
> of the code independently, there is no central method, which will give a
> consistent answer.
> >
> > In Trillian we take a micro-management approach and have a custom module
> which will return the least used cluster, the least used host or the least
> used host in a given cluster.  With that info we place VMs on a specific
> hosts - keeping virtualised hypervisors in the same cluster (least used) so
> that processor types match, and all other VMs on the least used hosts.
> >
> > For cross-cluster migrations (VMs and/or storage) I think that most
> times people want to move from cluster A to the least used
> (cluster/storage) in cluster B - making them choose which host/pool is
> actually unhelpful.
> >
> > #scopecreep - sorry Pierre-Luc
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Will Stevens 
> > Sent: 06 September 2018 19:45
> > To: dev@cloudstack.apache.org; Marc-Andre Jutras 
> > Subject: Re: [DISCUSS] deployment planner improvement
> >
> > If I remember correctly, we see similar issues on VMware.  Marcus, have
> you seen similar behavior on VMware?  I think I remember us having to
> manually vMotion a lot of VMs very often...
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > <https://goo.gl/NYZ8KK>
> >
> >
> > On Thu, Sep 6, 2018 at 2:34 PM Pierre-Luc Dion 
> wrote:
> >
> >> Hi,
> >>
> >> I'm working with a University in Montreal and we are looking at
> >> working together to improve the deployment planner. Mainly for post
> >> VM.CREATE tasks.
> >> Because  what we observed with cloudstack, in our case with XenServer,
> >> overtime, a cluster will become unbalanced in therm of workload, vm HA
> >> will move VMs all over the the cluster which cause hotspot inside a
> cluster.
> >> Also, when performing maintenance  xenmotion of VM spread them in the
> >> cluster but does not consider host usage and at the end of a
> >> maintenance it require manual operation to repopulate VMs on the last
> >> host updated.  OS preference not taken into account  except for
> VM.CREATE.
> >>
> >> So,
> >> I'd like to work on improving VMs dispersion during and post outage
> >> and maintenances. when a cluster resources are added or removed.
> >>
> >> Would you have any more requirement, we will document a feature spec
> >> in the wiki which I believe it's still a requirement ?
> >>
> >> Does using KVM have similar issues over time?
> >>
> >> I don't think it would make sense to cloudstack to automatically take
> >> decision on moving VMs but for now create report of recommended action
> >> to do and provide steps to do them. tbd.
> >>
> >> Cheers,
> >>
> >> PL
> >>
>
>

Re: Deploying VM with custom CPU and RAM

[Pierre-Luc Dion]

with cloudmonkey, it look like this:
details[0].cpuNumber=2 details[0].cpuSpeed=1000 details[0].memory=1024
rootdisksize=15

PL


On Sun, Sep 9, 2018 at 8:10 AM Fariborz Navidan 
wrote:

> Thank you, I just cheked apilog.log and found the parameter names.
>
> On Sun, Sep 9, 2018 at 2:41 PM Ivan Kudryavtsev 
> wrote:
>
> > Hi, why don't you just track RESTful API call sent thru API in Cloudstack
> > UI. Just click F12 in Chrome and trace the call.
> >
> > вс, 9 сент. 2018 г., 16:57 Fariborz Navidan :
> >
> > > Hello,
> > >
> > > I have created a customizable service offering in cloudstack and want
> to
> > > deploy VM via deployVirtualMachine() API call. If I specify id of
> custom
> > > service offering, I will need to specify cpu cores and memory, It is
> not
> > > documented how should I fill those parameters I have tried
> > > details[0].cpunumber=&details[0].cpuspeed=1000 still I get Invalid cpu
> > > cores value. How do I specify cpu cores?
> > >
> > > Thanks in advance.
> > >
> >
>

Re: SSL offload in the VR

[Pierre-Luc Dion]

Hey Paul, I'm not aware the vr support ssl offload. What you are trying to
achieve, there might be a work around.

Le mar. 20 nov. 2018 07 h 08, Paul Angus  a
écrit :

> Apologies if my GitHub foo has abandoned me (it wouldn’t me the first
> time);
>
> I searched for files which contained the API command
> ‘assignCertToLoadBalancer’ and found ‘AssignCertToLoadBalancerCmd.java’
>
> According to the history it was first committed as part of PR #2283
> “CLOUDSTACK-10105: Use maven standard project structure in all projects” [1]
>
>
> https://github.com/apache/cloudstack/commits/1d05fead49f5c856257a741b07122f5633d2e359/api/src/main/java/org/apache/cloudstack/api/command/user/loadbalancer/AssignCertToLoadBalancerCmd.java
>
> again, sorry if I’ve misread or misinterpreted the history…
>
> Kind regards,
>
> Paul Angus
>
> From: Marc-Aurèle Brothier 
> Sent: 20 November 2018 11:23
> To: Paul Angus 
> Cc: dev@cloudstack.apache.org
> Subject: Re: SSL offload in the VR
>
> Hi Paul,
>
> What made you think so? I haven’t pushed any change related to the VR. At
> Exoscale, we removed the VR entirely instead and moved the services down at
> the HV level.
>
> Kind regards,
> Marc-Aurèle
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> On 20 Nov 2018, at 09:04, Paul Angus  paul.an...@shapeblue.com>> wrote:
> Hi Marc-Aurèle,
>
> As far as I can tell, I believe that you added the ability to upload an
> SSL certificate to the VR in 4.11
> I can’t find any user documentation for it in our Wiki or the in
> read-the-docs.
> I guess it’s something that you use at Exoscale, could you do a pull
> request to cloudstack-documentation or forward me some documentation which
> I can then add to the users documentation.
>
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>

Re: SSL offload in the VR

[Pierre-Luc Dion]

Hi Paul, ok I was not aware of that new feature. Is it wanted to support lb
on sourceNAT IP has in your screenshot?


Le mer. 21 nov. 2018 03 h 27, Paul Angus  a
écrit :

> Thanks @Pierre-Luc Dion and @jaya...@apache.org,
>
> My 'problem' is that being able to add an SSL cert to a VR loadbalancer
> has appeared from nowhere in the 4.11 branch. (easiest explained with a
> screen snip):
>
> https://imgur.com/a/r7zxA0b
>
> ... which led me to finding the assignCertToLoadBalancer API.
>
> I can't find a specific PR for it, or anything in the cwiki, and nothing
> in our read-the-docs...
> So I'm trying to find the author, so we can back fit some documentation,
> rather than trying to reverse engineer it out of the code/trial and error.
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jayapal Uradi 
> Sent: 21 November 2018 04:31
> To: dev@cloudstack.apache.org
> Subject: Re: SSL offload in the VR
>
> What I remember is ssl offload feature  added for netscaler  and
> assignCertToLoadBalancer API added during that time.
>
> -Jayapal
>
> > On 21-Nov-2018, at 5:06 AM, Pierre-Luc Dion  wrote:
> >
> > Hey Paul, I'm not aware the vr support ssl offload. What you are
> > trying to achieve, there might be a work around.
> >
> > Le mar. 20 nov. 2018 07 h 08, Paul Angus  a
> > écrit :
> >
> >> Apologies if my GitHub foo has abandoned me (it wouldn’t me the first
> >> time);
> >>
> >> I searched for files which contained the API command
> >> ‘assignCertToLoadBalancer’ and found ‘AssignCertToLoadBalancerCmd.java’
> >>
> >> According to the history it was first committed as part of PR #2283
> >> “CLOUDSTACK-10105: Use maven standard project structure in all
> >> projects” [1]
> >>
> >>
> >> https://github.com/apache/cloudstack/commits/1d05fead49f5c856257a741b
> >> 07122f5633d2e359/api/src/main/java/org/apache/cloudstack/api/command/
> >> user/loadbalancer/AssignCertToLoadBalancerCmd.java
> >>
> >> again, sorry if I’ve misread or misinterpreted the history…
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >> From: Marc-Aurèle Brothier 
> >> Sent: 20 November 2018 11:23
> >> To: Paul Angus 
> >> Cc: dev@cloudstack.apache.org
> >> Subject: Re: SSL offload in the VR
> >>
> >> Hi Paul,
> >>
> >> What made you think so? I haven’t pushed any change related to the
> >> VR. At Exoscale, we removed the VR entirely instead and moved the
> >> services down at the HV level.
> >>
> >> Kind regards,
> >> Marc-Aurèle
> >>
> >>
> >> paul.an...@shapeblue.com
> >> www.shapeblue.com
> >> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >>
> >>
> >>
> >> On 20 Nov 2018, at 09:04, Paul Angus  >> paul.an...@shapeblue.com>> wrote:
> >> Hi Marc-Aurèle,
> >>
> >> As far as I can tell, I believe that you added the ability to upload
> >> an SSL certificate to the VR in 4.11 I can’t find any user
> >> documentation for it in our Wiki or the in read-the-docs.
> >> I guess it’s something that you use at Exoscale, could you do a pull
> >> request to cloudstack-documentation or forward me some documentation
> >> which I can then add to the users documentation.
> >>
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >>
> >> paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
> >> www.shapeblue.com<http://www.shapeblue.com>
> >> @shapeblue
> >>
> >>
> >>
> >>
>
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is
> the property of Accelerite, a Persistent Systems business. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Accelerite, a Persistent Systems business does not accept any
> liability for virus infected mails.
>

Re: Quetion about API 'revertSnapshot'

[Pierre-Luc Dion]

Hi,

I think it work on XenServer too the revert if a VM snapshot, at least, it
used to work. but I'm not sure if this API is for revert disk snapshot or
vm snapshot.


On Fri, Dec 21, 2018 at 2:52 AM Haijiao <18602198...@163.com> wrote:

> Hi，All
>
> Maybe it’s a stupid question, but from the CloudStack API docs,  the API
> ‘revertSnapshot’ is ONLY supported with KVM, but not others, e.g. XenServer
> or VMware .
>
> Is there any special reason for this ?  Shall we expect this feature
> included in coming release ACS ?
>
> http://cloudstack.apache.org/api/apidocs-4.11/apis/revertSnapshot.html
>
> Thanks!



-- 

*Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal
t 1.888.796.8364 ext. 1403


<https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email>

Re: Introduction

[Pierre-Luc Dion]

Re-welcome Andrija !

On Fri, Jan 11, 2019 at 6:22 AM Dag Sonstebo 
wrote:

> Welcome again Andrija - great to have you onboard!
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
> On 11/01/2019, 10:49, "Andrija Panic" 
> wrote:
>
> Hi all,
>
> I would like to take this opportunity to (re)introduce myself - some
> of you already know me from mailing list as Andrija Panic from HIAG/Safe
> Swiss Cloud.
>
> I have moved forward and joined a great team in ShapeBlue as a Cloud
> Architect and looking forward to further endeavors with CloudStack.
> FTR - I'm based in Belgrade, Serbia and been playing with CloudStack
> for last 5 years in production.
>
> Cheers,
> Andrija Panić
>
> andrija.pa...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

-- 

*Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal
t 1.888.796.8364 ext. 1403


<https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email>

Re: Dropping Nuage Networks support

[Pierre-Luc Dion]

Hi Kris,

Thanks a lot for your contributions, I hope you will remain close to our
community!




On Fri, Jan 25, 2019 at 3:33 PM Wei ZHOU  wrote:

> Hi Kris,
>
> It was nice to meet you some times and see your contributions to the
> project. Thank you and your colleagues for all your hard work.
>
> All the best in the future !
>
> -Wei
>
>
> Kris Sterckx  于2019年1月25日周五 下午7:14写道：
>
> > Folks,
> >
> >
> >
> > A management decision within Nuage Networks / Nokia has been made for
> > dropping CloudStack support in the upcoming release.
> >
> > With that, we have been working at a clean cut, taking out Nuage SDN
> > support from the code, as the last thing we want would be leaving
> > unsupported/broken code in the repo. Obviously, all generically
> applicable
> > contributions remain – only the Nuage specifics are taken out. Some of
> > these generic contributions include per-NIC extra DHCP options support,
> > extended Config Drive support (both discussed at the Miami CCC) and
> > Physical Network Migration (presented at the last Montreal CCC).
> >
> > The following PR has been uploaded, pending your review:
> >
> >
> > https://github.com/apache/cloudstack/pull/3146
> >
> >
> >
> > Together with Frank and Raf, I would like to thank everyone for the great
> > collaboration, the time we spent at conferences/meetups and the overall
> joy
> > we had. And I hope our ways to further cross.
> >
> > Keep up the great work.
> >
> >
> >
> > Kris
> >
>

Re: Release schedule for CloudStack CloudMonkey v6.0.0

[Pierre-Luc Dion]

+1 !

https://www.shapeblue.com/whats-coming-in-the-new-cloudmonkey-6-0/


On Tue, Feb 12, 2019 at 4:33 AM Rohit Yadav 
wrote:

> All,
>
>
> I would like to invite everyone for a final round of testing before
> cloudmonkey v6.0.0 RC1 can be cut for voting.
>
> Proposed timeline:
>
>
> - Test, fix bugs, update documentation and stabilize: Until 24 Feb 2019
>
> - Start RC1: Monday 25 Feb 2019
>
>
> Kindly test the latest cloudmonkey (testing) v6.0.0-beta3:
> https://github.com/apache/cloudstack-cloudmonkey/releases
>
> And help report issues:
> https://github.com/apache/cloudstack-cloudmonkey/issues
>
>
> Recent blog: https://www.shapeblue.com/whats-coming-in-cloudmonkey-6-0/
>
>
> Thanks and regards,
>
> Rohit Yadav
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.0.0

[Pierre-Luc Dion]

+1

basic test on 6.0.0 but using the go based cmk for few weeks already.

On Mon, Mar 11, 2019 at 6:49 AM Andrija Panic 
wrote:

> +1
>
> Somewhat limited testing, but played with previous beta builds - and all
> minor issues are fixed in this one - no new problems found.
>
> andrija.pa...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Dag Sonstebo 
> Sent: 11 March 2019 11:28
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Release Apache CloudStack CloudMonkey 6.0.0
>
> +1
>
> Tested and works well, no issues found. Navigation is greatly improved
> with options menus now more intuitive and selections with enter key allowed.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
> On 11/03/2019, 09:51, "Boris Stoyanov" 
> wrote:
>
> +1
> Played with it locally, didn’t had any issues. All controls seems
> working.
>
>
> boris.stoya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
> > On 11 Mar 2019, at 11:25, Wido den Hollander  wrote:
> >
> > +1
> >
> > Tested it locally on my laptop and does the things I do with it.
> >
> > I couldn't find anything which didn't work.
> >
> > Wido
> >
> > On 3/11/19 8:07 AM, Rohit Yadav wrote:
> >> All,
> >>
> >>
> >> Due to the lack of any testing/voting, the RC1 voting window will
> stay open indefinitely until lazy consensus/majority is met or a bug is
> reported requiring RC2. Thanks.
> >>
> >>
> >>
> >> Regards,
> >>
> >> Rohit Yadav
> >>
> >> Software Architect, ShapeBlue
> >>
> >> https://www.shapeblue.com
> >>
> >> 
> >> From: Rohit Yadav 
> >> Sent: Tuesday, March 5, 2019 5:45:01 PM
> >> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> >> Subject: [VOTE] Release Apache CloudStack CloudMonkey 6.0.0
> >>
> >> Hi All,
> >>
> >> I've created a 6.0.0 release of CloudMonkey, with the following
> artifacts
> >> up for a vote:
> >>
> >> Git Branch and Commit SHA:
> >>
> https://github.com/apache/cloudstack-cloudmonkey/commit/74ff37cffc1d8bb3652f6887faa770d933ffe768
> >>
> >> Commit: 74ff37cffc1d8bb3652f6887faa770d933ffe768
> >>
> >> Github pre-release (for testing, contains changelog,
> artifacts/binaries to
> >> test, checksums/usage details):
> >> https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.0.0
> >>
> >> Source release (checksums and signatures are available at the same
> >> location):
> >> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.0.0
> >>
> >> PGP release keys (signed using
> 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>
> >> The vote will be open for 72 hours.
> >>
> >> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> >> "(binding)" with their vote?
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> ] -1 disapprove (and the reason why)
> >>
> >> Regards,
> >> Rohit Yadav
> >>
> >> rohit.ya...@shapeblue.com
> >> www.shapeblue.com
> >> Amadeus House, Floral Street, London  WC2E 9DPUK
> >> @shapeblue
> >>
> >>
> >>
>
>
>
>

new contributor guide

[Pierre-Luc Dion]

Hi team,

I was wondering if someone would have an idea of which doc a new
contributor should look at when someone want to start contributing to
cloudstack? I haven't contribute in code for some time and I'm lost, and
while working with a university to help us on contributing to cloudstack I
realise we have no easy doc as a new dev member.

things like,
* how to setup a dev station, (devcloud? which version?)
* how to contribute bug fix
* how to contribute new feature.

If we have such info sweet, otherwise, I'm willing to update this part.

Re: new contributor guide

[Pierre-Luc Dion]

Thanks Marco,

I'll look at those!

On Fri, Mar 22, 2019 at 9:31 AM Marc-Aurèle Brothier  wrote:

> Hi Pierre-Luc,
>
> You can have a look at those links for the install and development setup:
> - https://github.com/apache/cloudstack/blob/master/INSTALL.md
>
> - https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md
>
> Those should get you started. If those aren’t enough and/or you get stuck,
> come back to the community so we can update those with the missing stuff.
>
> A good first contribution candidate could be changes to those docs as it’s
> easier to get those extra missing details as a newbie to a project.
>
> Marco
>
> > On 22 Mar 2019, at 13:48, Pierre-Luc Dion  wrote:
> >
> > Hi team,
> >
> > I was wondering if someone would have an idea of which doc a new
> > contributor should look at when someone want to start contributing to
> > cloudstack? I haven't contribute in code for some time and I'm lost, and
> > while working with a university to help us on contributing to cloudstack
> I
> > realise we have no easy doc as a new dev member.
> >
> > things like,
> > * how to setup a dev station, (devcloud? which version?)
> > * how to contribute bug fix
> > * how to contribute new feature.
> >
> > If we have such info sweet, otherwise, I'm willing to update this part.
>

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

[Pierre-Luc Dion]

I agree, it should simplify builds too.


On Mon, Apr 15, 2019 at 7:17 AM Andrija Panic 
wrote:

> +1
>
> CentOS 6 was a pain to make any newer features works, in regards to ancient
> qemu/libvirt and so on.
>
> On Mon, 15 Apr 2019 at 10:05, Wido den Hollander  wrote:
>
> >
> >
> > On 4/15/19 9:44 AM, Rohit Yadav wrote:
> > > All,
> > >
> > >
> > > With CentOS8 around the corner to be released sometime around the
> > summer, I would like to propose to deprecate CentOS6 as support
> management
> > server host distro and KVM host distro. Non-systemd enabled Ubuntu
> releases
> > have been already deprecated [1].
> > >
> > >
> > > The older CentOS6 version would hold us back as we try to adapt, use
> and
> > support newer JRE version, kvm/libvirt version, the Linux kernel, and
> > several other older dependencies. Both CentOS6 and RHEL6 have reached EOL
> > on May 10th, 2017 wrt full updates [1].
> > >
> > >
> > > If we don't have any disagreements, I propose we remove el6 packaging
> > support in the next major release - 4.13. But, if there are users and
> > organisations that will be badly impacted, let 4.13 be the last of
> releases
> > to support el6 and we definitely remove el6 support in 4.14.
> > >
> > > What are your thoughts?
> >
> > I agree! EL6 is just no longer suited for development. Good suggestion.
> >
> > Wido
> >
> > >
> > >
> > > [1] EOL date wiki reference:
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hypervisor+and+Management+Server+OS+EOL+Dates
> > >
> > >
> > >
> > > Regards,
> > >
> > > Rohit Yadav
> > >
> > > Software Architect, ShapeBlue
> > >
> > > https://www.shapeblue.com
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> >
>
>
> --
>
> Andrija Panić
>

https://builds.cloudstack.org/

[Pierre-Luc Dion]

Hello community,

I was wondering if we still use jenkins service from
https://builds.cloudstack.org/ to create builds?
I have not maintain that service for quite some time so if it's not being
used I would decommission it. It was going to be a replacement of
jenkins.b.a.c.com a while back, but since then we moved into github and
since then, I kind of lost track.

I think this is still creating docker images:
* https://hub.docker.com/r/cloudstack/simulator
* https://hub.docker.com/r/cloudstack/marvin

Based on the number of pull, marvin is clearly unpopular but simulator have
~10k pulls...

Thanks,

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

[Pierre-Luc Dion]

+1

On Tue, May 21, 2019 at 8:18 AM Wido den Hollander  wrote:

> +1
>
> On 5/21/19 11:40 AM, Rohit Yadav wrote:
> > All,
> >
> >
> > Thank you for your feedback and discussions. From what we've discussed
> so far, we've lazy consensus that nobody wants to use el6 or are limited to
> upgrade to el7/el8 due to potential risks.
> >
> >
> > Moving forward I put forth the following for voting:
> >
> >
> > - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last
> ones to support el6 packaging both for the management server and KVM host,
> but users are discouraged from using them
> >
> > - Next major release (4.13.0.0) will document in its release notes that
> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
> and onwards
> >
> > - After 4.13.0.0 is released, we will remove el6 related specs,
> packaging scripts etc. from the codebase in the master branch
> >
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> >
> > ** PMCs kindly add binding to your votes, thanks.
> >
> >
> > Thanks.
> >
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> >
> > 
> > From: Erik Weber 
> > Sent: Wednesday, April 24, 2019 19:32
> > To: dev
> > Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
> >
> > CentOS7 was released 5 years ago, upgrading is long overdue anyway.
> > Realistically the next CloudStack release won't be out the door for
> > another ~4-6 months either.
> >
> > --
> > Erik
> >
> > On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
> >  wrote:
> >>
> >> According to https://en.wikipedia.org/wiki/CentOS
> >>
> >> CentOS 6 EOL is 2020
> >> CentOS 7 EOL is 2024
> >>
> >>
> >> +1 for removing support for CentOS 6.
> >>
> >> As Erik pointed out the sites running CentOS6 will have to move soon in
> >> any event and it is probably better to do it now when there is still a
> >> lot of current expertise and information available about how to do it
> >> and how to make any changes to applications.
> >>
> >> Upgrading in a project that is under your control is usually easier than
> >> one forced on you by a security issue or an operational failure.
> >>
> >> Ron
> >>
> >> On 4/24/19 3:24 AM, Erik Weber wrote:
> >>> As an operations guy I can understand the want for future updates and
> >>> not upgrading, but with the release plan of RHEL/CentOS I don't find
> >>> it feasible.
> >>>
> >>> RHEL6 is 8 years old (and is still running kernel 2.6!) and isn't
> >>> scheduled to be fully EOL until 2024.
> >>>
> >>> It is true that upgrading requires some effort (and risk) from
> >>> operators, but this is work they eventually have to do anyway, so it's
> >>> not a matter of /if/ they have to do it, but rather when.
> >>>
> >>> It is also true that current CloudStack releases should continue to
> >>> work, it's also possible that someone might back port future fixes to
> >>> a RHEL6 compatible fork (you're more than welcome to).
> >>>
> >>> I'd vote +1 to remove support for el6 packaging.
> >>>
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>

Re: Secondary Storage VM timeout issue every hour

[Pierre-Luc Dion]

Do you have a load balancer in front of cloudstack? Did you set the global
settings "host" to the ip of the mgmt server?


Le jeu. 25 juill. 2019 03 h 24, Rakesh Venkatesh 
a écrit :

> Hello People
>
>
> I have a strange issue where mgt server times out to send a command to
> secondary storage VM every hour and because of this UI won't be accessible
> for a short duration of time. Sometimes I have to restart mgt server to get
> it back to working state and sometimes I don't need to restart it. I also
> see some exceptions while fetching the storage stats.
>
>
> The log says secondary storage VM is lagging behind mgt server in ping and
> it sends a disconnect message to other components. Can you let me know how
> to troubleshoot this issue? I destroyed the secondary storage VM but the
> issue still persists. I checked the date/time on the mgt server and SSVM
> and they are same. This is happening for quite a few days now. Below are
> the logs
>
>
>
> 2019-07-25 04:01:22,769 INFO  [c.c.a.m.AgentManagerImpl]
> (AgentMonitor-1:ctx-c33dbe74) (logid:5442158c) Found the following agents
> behind on ping: [183]
> 2019-07-25 04:01:22,775 WARN  [c.c.a.m.AgentManagerImpl]
> (AgentMonitor-1:ctx-c33dbe74) (logid:5442158c) Disconnect agent for
> CPVM/SSVM due to physical connection close. host: 183
> 2019-07-25 04:01:22,778 INFO  [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Host 183 is disconnecting
> with event ShutdownRequested
> 2019-07-25 04:01:22,781 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) The next status of agent
> 183is Disconnected, current status is Up
> 2019-07-25 04:01:22,781 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Deregistering link for 183
> with state Disconnected
> 2019-07-25 04:01:22,781 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Remove Agent : 183
> 2019-07-25 04:01:22,781 DEBUG [c.c.a.m.ConnectedAgentAttache]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Processing Disconnect.
> 2019-07-25 04:01:22,782 DEBUG [c.c.a.m.AgentAttache]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Seq
> 183-7541559051008607242: Sending disconnect to class
> com.cloud.agent.manager.SynchronousListener
> 2019-07-25 04:01:22,782 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer
> 2019-07-25 04:01:22,782 DEBUG [c.c.u.n.NioConnection]
> (pool-2-thread-1:null) (logid:) Closing socket Socket[addr=/172.30.32.16
> ,port=38250,localport=8250]
> 2019-07-25 04:01:22,782 DEBUG [c.c.a.m.AgentAttache]
> (StatsCollector-2:ctx-b55657a9) (logid:dafc4881) Seq
> 183-7541559051008607242: Waiting some more time because this is the current
> command
> 2019-07-25 04:01:22,782 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.hypervisor.hyperv.discoverer.HypervServerDiscoverer
> 2019-07-25 04:01:22,783 DEBUG [c.c.a.m.AgentAttache]
> (StatsCollector-2:ctx-b55657a9) (logid:dafc4881) Seq
> 183-7541559051008607242: Waiting some more time because this is the current
> command
> 2019-07-25 04:01:22,783 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.deploy.DeploymentPlanningManagerImpl
> 2019-07-25 04:01:22,783 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.network.security.SecurityGroupListener
> 2019-07-25 04:01:22,783 INFO  [c.c.u.e.CSExceptionErrorCode]
> (StatsCollector-2:ctx-b55657a9) (logid:dafc4881) Could not find exception:
> com.cloud.exception.OperationTimedoutException in error code list for
> exceptions
> 2019-07-25 04:01:22,783 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: org.apache.cloudstack.engine.orchestration.NetworkOrchestrator
> 2019-07-25 04:01:22,783 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.vm.ClusteredVirtualMachineManagerImpl
> 2019-07-25 04:01:22,783 WARN  [c.c.a.m.AgentAttache]
> (StatsCollector-2:ctx-b55657a9) (logid:dafc4881) Seq
> 183-7541559051008607242: Timed out on null
> 2019-07-25 04:01:22,783 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.storage.listener.StoragePoolMonitor
> 2019-07-25 04:01:22,784 DEBUG [c.c.a.m.AgentAttache]
> (StatsCollector-2:ctx-b55657a9) (logid:dafc4881) Seq
> 183-7541559051008607242: Cancelling.
> 2019-07-25 04:01:22,784 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentTaskPool-1:ctx-66de2057) (logid:841d2a63) Sending Disconnect to
> listener: com.cloud.storage.secondary.SecondaryStorageListener
> 2019-07-25 04:01:22,784 DEBUG [c.c.a.m.AgentManage

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Pierre-Luc Dion]

hello,

That look interesting, but any plan on doing the other way around too?
Like having k8s consume CloudStack resources so a k8s cluster could update
load-balancing service of a VPC or other network service from cloudstack,
attach Data-volumes and such..



On Tue, Sep 24, 2019 at 2:42 AM Abhishek Kumar 
wrote:

> Hi all,
>
> I would like to propose developing a plugin for Kubernetes integration in
> CloudStack, can be named CloudStack Kubernetes Service plugin.
> I've written down an initial design document for it here,
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service
> Please review and provide your thoughts and suggestions.
>
> Regards,
>
>
> Abhishek Kumar
>
> Software Engineer
>
> ShapeBlue
>
> abhishek.ku...@shapeblue.com
>
> www.shapeblue.com
>
> abhishek.ku...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

-- 

*Pierre-Luc *

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Pierre-Luc Dion]

Hi Rohit, Nux,

Thanks Rohit for cloudstack-provider, that's exactly it ! :-D
Nux, I agree with your opinion, but there is a lot of interest for k8s and
seams like
a lot of organisations are moving to container based infrastructures to
standardized their deployment.

if we want to extent the discussion to function as a service, would you
guys see a possibility for us to
be more aligned or more deployment friendly for Openwhisk ?

Cheers,


On Wed, Sep 25, 2019 at 6:54 AM Will Stevens  wrote:

> We see huge demand for K8s in our customer base. Just a note...
>
> On Wed, Sep 25, 2019, 4:03 AM Nux!  wrote:
>
> > Do you guys see high demand for K8s?
> >  From where I'm looking it seems to be going the way of Openstack, loads
> > of hype, overcomplicated, near-impossible to upgrade.
> > Not sure if it's worth investing resources for this.
> >
> > Lucian
> >
> > ---
> > Sent from the Delta quadrant using Borg technology!
> >
> > On 2019-09-24 07:41, Abhishek Kumar wrote:
> > > Hi all,
> > >
> > > I would like to propose developing a plugin for Kubernetes integration
> > > in CloudStack, can be named CloudStack Kubernetes Service plugin.
> > > I've written down an initial design document for it here,
> > >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service
> > > Please review and provide your thoughts and suggestions.
> > >
> > > Regards,
> > >
> > >
> > > Abhishek Kumar
> > >
> > > Software Engineer
> > >
> > > ShapeBlue
> > >
> > > abhishek.ku...@shapeblue.com
> > >
> > > www.shapeblue.com<http://www.shapeblue.com>
> > >
> > > abhishek.ku...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> >
>


-- 

*Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal
t 1.888.796.8364 ext. 1403


<https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email>

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Pierre-Luc Dion]

Hi Paul,

Yeah, was bad timing for the CCCNA this year unfortunately :-(,  I'm not
sure I'm curious to see how cloudstack could become more
"other Apache products friendly" but I don't have particular use case
compared to k8s integration. Has you are suggesting,
would probably make sense to use Helm to deploy any other application stack.

btw, we are still working on the Canonical MaaS integration, a bit more
challenging than anticipated...


To get back to a *Kubernetes Service plugin*:
To me, as a user of cloudstack at the moment, If I deploy a k8s cluster, I
need to deploy monstrous instances for worker nodes.
which doesn't make sense if I'm a cloud consumer. So I think we need to
solve something challenging: a k8s service that would scale has needed
while keeping in mind redundancy of worker nodes without sacrifice on
security. Is the worker node is part of the ongoing work or it's more about
offering a k8s master and api infrastructure to a user ?

An easy path would be some kind of shared worker nodes pool but that
involve possible security risk unless you would trust users that consume
those workers.


On Wed, Sep 25, 2019 at 10:15 AM Paul Angus 
wrote:

> Hi Pierre-Luc,
>
> (we missed you at CCCNA!) How are you seeing CloudStack being more
> deployment friendly?  What you do think that we could do on top of creating
> the Kubenetes Cluster to begin with?
> [thinking out loud - we could pre-package Tiller to make it easier to
> deploy openWhisk via Helm charts ? ]
>
> Kind regards
>
>
> Paul.
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion 
> Sent: 25 September 2019 13:37
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
>
> Hi Rohit, Nux,
>
> Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I agree
> with your opinion, but there is a lot of interest for k8s and seams like a
> lot of organisations are moving to container based infrastructures to
> standardized their deployment.
>
> if we want to extent the discussion to function as a service, would you
> guys see a possibility for us to be more aligned or more deployment
> friendly for Openwhisk ?
>
> Cheers,
>
>
> On Wed, Sep 25, 2019 at 6:54 AM Will Stevens 
> wrote:
>
> > We see huge demand for K8s in our customer base. Just a note...
> >
> > On Wed, Sep 25, 2019, 4:03 AM Nux!  wrote:
> >
> > > Do you guys see high demand for K8s?
> > >  From where I'm looking it seems to be going the way of Openstack,
> > > loads of hype, overcomplicated, near-impossible to upgrade.
> > > Not sure if it's worth investing resources for this.
> > >
> > > Lucian
> > >
> > > ---
> > > Sent from the Delta quadrant using Borg technology!
> > >
> > > On 2019-09-24 07:41, Abhishek Kumar wrote:
> > > > Hi all,
> > > >
> > > > I would like to propose developing a plugin for Kubernetes
> > > > integration in CloudStack, can be named CloudStack Kubernetes
> Service plugin.
> > > > I've written down an initial design document for it here,
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kube
> > rnetes+Service
> > > > Please review and provide your thoughts and suggestions.
> > > >
> > > > Regards,
> > > >
> > > >
> > > > Abhishek Kumar
> > > >
> > > > Software Engineer
> > > >
> > > > ShapeBlue
> > > >
> > > > abhishek.ku...@shapeblue.com
> > > >
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > >
> > > > abhishek.ku...@shapeblue.com
> > > > www.shapeblue.com
> > > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> >
>
>
> --
>
> *Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal
> t 1.888.796.8364 ext. 1403
>
>
> <
> https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email
> >
>


--

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Pierre-Luc Dion]

Make sense for the proposed implementation, would it handle redundant
master?
How would the k8s cluster would be created, using Rancher tools, kubectl or
other?

so far, the small part I understand from MaaS, it could be very interesting
to integrate it to cloudstack in a way where it could be use to  scale
Hypervisor host, specially KVM nodes.


On Wed, Sep 25, 2019 at 10:47 AM Paul Angus 
wrote:

> The proposed implementation will create a master and n worker nodes.
> It will also support (graceful) cluster resizing, the next step would be
> to enable the CloudStack plugin for Kubernetes to allow Kubernetes to drive
> that scaling, so that you can scale with demand rather than needing to
> oversize you environment to begin with.
>
> I've been keeping MaaS in mind as way of doing baremetal Kubernetes along
> side VM based Kubernetes clusters.  Interestingly a few people that I have
> spoken to have said that they prefer the use of VMs, because whole servers
> as the unit of scale is often very wasteful, unless you 'share' them which
> has all sorts of security implications...
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion 
> Sent: 25 September 2019 15:31
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
>
> Hi Paul,
>
> Yeah, was bad timing for the CCCNA this year unfortunately :-(,  I'm not
> sure I'm curious to see how cloudstack could become more "other Apache
> products friendly" but I don't have particular use case compared to k8s
> integration. Has you are suggesting, would probably make sense to use Helm
> to deploy any other application stack.
>
> btw, we are still working on the Canonical MaaS integration, a bit more
> challenging than anticipated...
>
>
> To get back to a *Kubernetes Service plugin*:
> To me, as a user of cloudstack at the moment, If I deploy a k8s cluster, I
> need to deploy monstrous instances for worker nodes.
> which doesn't make sense if I'm a cloud consumer. So I think we need to
> solve something challenging: a k8s service that would scale has needed
> while keeping in mind redundancy of worker nodes without sacrifice on
> security. Is the worker node is part of the ongoing work or it's more about
> offering a k8s master and api infrastructure to a user ?
>
> An easy path would be some kind of shared worker nodes pool but that
> involve possible security risk unless you would trust users that consume
> those workers.
>
>
> On Wed, Sep 25, 2019 at 10:15 AM Paul Angus 
> wrote:
>
> > Hi Pierre-Luc,
> >
> > (we missed you at CCCNA!) How are you seeing CloudStack being more
> > deployment friendly?  What you do think that we could do on top of
> > creating the Kubenetes Cluster to begin with?
> > [thinking out loud - we could pre-package Tiller to make it easier to
> > deploy openWhisk via Helm charts ? ]
> >
> > Kind regards
> >
> >
> > Paul.
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion 
> > Sent: 25 September 2019 13:37
> > To: dev@cloudstack.apache.org
> > Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
> >
> > Hi Rohit, Nux,
> >
> > Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I
> agree
> > with your opinion, but there is a lot of interest for k8s and seams like
> a
> > lot of organisations are moving to container based infrastructures to
> > standardized their deployment.
> >
> > if we want to extent the discussion to function as a service, would you
> > guys see a possibility for us to be more aligned or more deployment
> > friendly for Openwhisk ?
> >
> > Cheers,
> >
> >
> > On Wed, Sep 25, 2019 at 6:54 AM Will Stevens 
> > wrote:
> >
> > > We see huge demand for K8s in our customer base. Just a note...
> > >
> > > On Wed, Sep 25, 2019, 4:03 AM Nux!  wrote:
> > >
> > > > Do you guys see high demand for K8s?
> > > >  From where I'm looking it seems to be going the way of Openstack,
> > > > loads of hype, overcomplicated, near-impossible to upgrade.
> > > > Not sure if it's worth investing resources for this.
> > > >
> > > > Lucian
> > > >
> > > > ---
> > > >

Re: vcpu socket configuration

[Pierre-Luc Dion]

Using cloudmonkey or cmk, you can specify the number of socket at the vm
create using : "details[0].cpu.corespersocket=6"
so if you define 8 vcpu with details[0].cpu.corespersocket=4  the vm will
have 4 sockets @2cores.

On Sun, Nov 24, 2019 at 8:41 AM li jerry  wrote:

> Hello All
>
> We found in the process of use, when the vcpu in service_offering is a
> multiple of 6, vm cpu socket =vcpu/6, when vcpu is a multiple of 4, vm cpu
> socket=vcpu/4
>
>
> Excuse me, why do we design this way?
>
> In my application scenario, there are restrictions on cpu socket, so I
> want to lock the socket to cpu socket=vcpu/2, what are the drawbacks? (Of
> course, I will exclude the singular vcpu)
>
>
>
>
> -Jerry
>

Re: vcpu socket configuration

[Pierre-Luc Dion]

When I used to use this command it was with XenServer has hypervisor, I've
never tested it with KVM. Also, make sure you use matching multiple of
vpcu/socket.
ie,  deploying 6 vcpu on 4 socket will not work.

On Mon, Nov 25, 2019 at 9:02 AM li jerry  wrote:

>
> After deploying the VM with the following command, the cpu socket is still
> invalid, but I saw cpu.corespersocket = 2 in the "Settings" of vm
>
>
> Ps :this is KVM Host
> cmk
> deploy virtualmachine zoneid=2bc73a3d-4c92-49da-b323-1142a45dca8c
> templateid=6802f4cb-2529-48f4-bba9-ff7d82db3ab9
> serviceofferingid=b8850bca-88b4-4378-ba70-e87546db58fd
> name=test-cpu-socket-02 networkids=e28d44cf-9179-4526-81b6-990ef31ec9be
> details[0].cpu.corespersocket=2
>
>
> cmk list vm
>
> "virtualmachine": [...
> {
>   "account": "admin",
>   "affinitygroup": [],
>   "cpunumber": 20,
>   "cpuspeed": 2000,
>   "cpuused": "0.05%",
>   "created": "2019-11-25T21:53:39+0800",
>   "details": {
> "Message.ReservedCapacityFreed.Flag": "false",
> "cpu.corespersocket": "2",
> "cpuOvercommitRatio": "4.0",
> "keyboard": "us",
> "memoryOvercommitRatio": "2.0"
>   },
>   "diskioread": 1,
>   "diskiowrite": 213,
>   "diskkbsread": 16,
>   "diskkbswrite": 4610,
>   "displayname": "test-cpu-socket-02",
>   "displayvm": true,
>   "domain": "ROOT",
>   "domainid": "602d9221-e184-11e8-9d95-4ab2a88c1305",
>   "guestosid": "c7a858b6-e184-11e8-9d95-4ab2a88c1305",
>   "haenable": true,
>   "hostid": "f0613074-9b79-4858-9dda-2453bca9c3e6",
>   "hostname": "hcicn03",
>   "hypervisor": "KVM",
>   "id": "f9e32a8c-1d27-4cff-b835-305b11c93fa5",
>   "instancename": "i-2-1133-VM",
>   "isdynamicallyscalable": false,
>   "memory": 4096,
>   "memoryintfreekbs": 755744,
>   "memorykbs": 4194304,
>   "memorytargetkbs": 4194304,
>   "name": "test-cpu-socket-02",
>   "networkkbsread": 0,
>   "networkkbswrite": 0,
>   "nic": [
> {
>   "broadcasturi": "vlan://835",
>   "extradhcpoption": [],
>   "gateway": "10.1.1.1",
>   "id": "d756de24-ac07-4ad4-8238-40f6d6f9b10c",
>   "ipaddress": "10.1.1.30",
>   "isdefault": true,
>   "isolationuri": "vlan://835",
>   "macaddress": "02:00:52:aa:00:08",
>   "netmask": "255.255.255.0",
>   "networkid": "e28d44cf-9179-4526-81b6-990ef31ec9be",
>   "networkname": "test-assistanz-mon",
>   "secondaryip": [],
>   "traffictype": "Guest",
>   "type": "Isolated"
> }
>   ],
>   "ostypeid": "c7a858b6-e184-11e8-9d95-4ab2a88c1305",
>   "passwordenabled": true,
>   "rootdeviceid": 0,
>   "rootdevicetype": "ROOT",
>   "securitygroup": [],
>   "serviceofferingid": "b8850bca-88b4-4378-ba70-e87546db58fd",
>   "serviceofferingname": "SP01-20C4G",
>   "state": "Running",
>   "tags": [],
>   "templatedisplaytext": "Include zabbix agent",
>   "templateid": "6802f4cb-2529-48f4-bba9-ff7d82db3ab9",
>   "templatename": "Centos 7 EN Zabbix",
>   "userid": "d608a7ba-e184-11e8-9d95-4ab2a88c1305",
>   "username": "admin",
>   "zoneid": "2bc73a3d-4c92-49da-b323-1142a45dca8c",
>   "zonename": "zone1"
> }
>   ]
> }
>
> -邮件原件-
> 发件人: Nii Apleh Lartey 
> 发送时间: 2019年11月25日 21:55
> 收件人: dev@cloudstack.apache.org
> 主题: Re: vcpu socket configuration
>
> You have a "p" and the end of "details"
>
> ____
> Fr

Re: vcpu socket configuration

[Pierre-Luc Dion]

templatedisplaytext": "Include zabbix agent",
>   "templateid": "6802f4cb-2529-48f4-bba9-ff7d82db3ab9",
>   "templatename": "Centos 7 EN Zabbix",
>   "userid": "d608a7ba-e184-11e8-9d95-4ab2a88c1305",
>   "username": "admin",
>   "zoneid": "2bc73a3d-4c92-49da-b323-1142a45dca8c",
>   "zonename": "zone1"
> }
>   ]
> }
>
> -邮件原件-
> 发件人: Nii Apleh Lartey mailto:niiap...@live.com>>
> 发送时间: 2019年11月25日 21:55
> 收件人: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
> 主题: Re: vcpu socket configuration
>
> You have a "p" and the end of "details"
>
> 
> From: li jerry mailto:div...@hotmail.com>>
> Sent: Monday, November 25, 2019 1:52 PM
> To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org> <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Subject: 回复: vcpu socket configuration
>
> Thank you,
>
>
>
> Socket doesn't work after I deploy VM with the following command
>
>
>
> cmk deploy virtualmachine zoneid=2bc73a3d-4c92-49da-b323-1142a45dca8c
> templateid=6802f4cb-2529-48f4-bba9-ff7d82db3ab9
> serviceofferingid=b8850bca-88b4-4378-ba70-e87546db58fd
> name=test-cpu-socket-02 networkids=e28d44cf-9179-4526-81b6-990ef31ec9be
> detailsp[0].cpu.corespersocket=2
>
>
>
>
>
> ps: serviceoffering
>
>
>
> (localcloud)  > list serviceofferings
> id=b8850bca-88b4-4378-ba70-e87546db58fd
>
> {
>
> "Count": 1,
>
> "serviceoffering": [
>
> {
>
> "cpunumber": 20,
>
> "cpuspeed": 2000,
>
> "created": "2019-08-09T11:11:20+0800",
>
> "defaultuse": false,
>
> "deploymentplanner": "FirstFitPlanner",
>
> "displaytext": "SP01-20C4G",
>
> "domain": "ROOT",
>
> "domainid": "602d9221-e184-11e8-9d95-4ab2a88c1305",
>
> "hosttags": "ha",
>
> "id": "b8850bca-88b4-4378-ba70-e87546db58fd",
>
> "iscustomized": false,
>
> "issystem": false,
>
> "isvolatile": false,
>
> "limitcpuuse": false,
>
> "memory": 4096,
>
> "name": "SP01-20C4G",
>
> "offerha": true,
>
> "provisioningtype": "thin",
>
> "serviceofferingdetails": {
>
> "domainid": "1"
>
> }
>
> "storagetype": "shared",
>
> "tags": "rbd01"
>
> }
>
> ]
>
> }
> -邮件原件-
> 发件人: Pierre-Luc Dion mailto:pdion...@apache.org>>
> 发送时间: 2019年11月25日 21:36
> 收件人: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
> 主题: Re: vcpu socket configuration
>
> Using cloudmonkey or cmk, you can specify the number of socket at the vm
> create using : "details[0].cpu.corespersocket=6"
> so if you define 8 vcpu with details[0].cpu.corespersocket=4  the vm will
> have 4 sockets @2cores.
>
> On Sun, Nov 24, 2019 at 8:41 AM li jerry  div...@hotmail.com>> wrote:
>
> > Hello All
> >
> > We found in the process of use, when the vcpu in service_offering is a
> > multiple of 6, vm cpu socket =vcpu/6, when vcpu is a multiple of 4, vm
> > cpu
> > socket=vcpu/4
> >
> >
> > Excuse me, why do we design this way?
> >
> > In my application scenario, there are restrictions on cpu socket, so I
> > want to lock the socket to cpu socket=vcpu/2, what are the drawbacks?
> > (Of course, I will exclude the singular vcpu)
> >
> >
> >
> >
> > -Jerry
> >
>

Re: CloudStack Kubernetes provider containers on DockerHub

[Pierre-Luc Dion]

hi, sorry for the late response,

I still have admin access to or cloudstack org on docker hub, [1]  if you
want admin access to it, provide me your account name on docker hub and
I'll add you to the admin group.
Quickly looking at it, it's more than overdue, unfortunately all our
containers there are outdated :-(

We also have apachecloudstack org name if it's preferable.

These 2 orgs are not subprojects of Apache orgs in docker hub, and probably
it would be better to use the apache orgs  ? I don't have any rights on
apache docker hub org.

Cheers,


[1] https://hub.docker.com/orgs/cloudstack

On Fri, Jan 10, 2020 at 3:07 AM Riepl, Gregor (SWISS TXT) <
gregor.ri...@swisstxt.ch> wrote:

> Hello and happy new year to everybody!
>
> The k8s provider[1] is still lacking built containers so people can use it
> directly.
> Were you able to figure out how to access the mentioned Docker hub
> accounts in the meantime?
>
> We can also create a new one if necessary...
>
> Thanks,
> Greg
>
>
> [1] https://github.com/apache/cloudstack-kubernetes-provider
>
> 
> From: Rohit Yadav 
> Sent: 01 October 2019 12:18
> To: dev@cloudstack.apache.org ; Pierre-Luc
> Dion ; Will Stevens ;
> gabrasc...@gmail.com ; Wido den Hollander <
> w...@widodh.nl>
> Subject: Re: CloudStack Kubernetes provider containers on DockerHub
>
> Thanks Gregor.
>
> Let me tag a few people that may have access to one of the following
> docker hub organizations:
>
> apache
> apachecloudstack
> cloudstack
>
>
> Can you grant access to me (my docker username is 'bhaisaab') and Gregor?
> Thanks.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Riepl, Gregor (SWISS TXT) 
> Sent: Tuesday, October 1, 2019 14:30
> To: dev@cloudstack.apache.org 
> Subject: CloudStack Kubernetes provider containers on DockerHub
>
> Hi everyone,
>
> We still need to publish the new
> https://github.com/apache/cloudstack-kubernetes-provider on a public
> container registry.
> It looks like the ASF and/or CloudStack project already have accounts on
> DockerHub:
> https://hub.docker.com/u/apache
> https://hub.docker.com/u/apachecloudstack
>
> Who has access to these organisations and can publish the provider there?
> The Github repository contains a suitable Dockerfile that we used with
> DockerHub before and shouldn't require any complicated repository setup.
>
> If possible, please give access to @rhtyd so he can take care of things.
>
> Thanks!
> Gregor
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Re: CloudStack Kubernetes provider containers on DockerHub

[Pierre-Luc Dion]

Hi Paul,

So we should not use our 2 account but use under apache one instead,
correct?  if so, I will remove all owner and projects from the 2 I've
created a while back. they are outdated anyway so better hiding them then
keep old stuff that can cause confusion.


On Sun, Jan 12, 2020 at 4:10 PM Sven Vogel  wrote:

> Hi Paul,
>
> I agree! I would do the same If it’s possible.
>
> Cheers
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> s.vo...@ewerk.com
> www.ewerk.com
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter
> Registergericht: Leipzig HRB 9065
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 2-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 12.01.2020 um 21:40 schrieb Paul Angus :
> >
> > Hey Guys,
> >
> > Actually I've been meaning to get round to sorting this. We need to
> remove 'our' docker hub account and use the Apache run one
> > https://hub.docker.com/u/apache
> >
> > This came up on the Board mailing list with another project. We'll need
> to align ourselves with the policy also.
> >
> >
> >
> > Kind regards
> >
> >
> > Paul.
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Sven Vogel 
> > Sent: 12 January 2020 14:07
> > To: dev 
> > Cc: Pierre-Luc Dion ; Pierre-Luc Dion <
> pd...@cloudops.com>; Will Stevens ;
> gabrasc...@gmail.com; Wido den Hollander 
> > Subject: Re: CloudStack Kubernetes provider containers on DockerHub
> >
> > Hi Guys,
> >
> > Should we also find a ways to put the passwords accessible for all
> committers or PMC like Youtube Account?
> >
> > Make that sense?
> >
> > Cheers
> >
> > Sven
> >
> >
> > __
> >
> > Sven Vogel
> > Teamlead Platform
> >
> > EWERK DIGITAL GmbH
> > Brühl 24, D-04109 Leipzig
> > P +49 341 42649 - 99
> > F +49 341 42649 - 98
> > s.vo...@ewerk.com
> > www.ewerk.com
> >
> > Geschäftsführer:
> > Dr. Erik Wende, Hendrik Schubert, Frank Richter
> > Registergericht: Leipzig HRB 9065
> >
> > Zertifiziert nach:
> > ISO/IEC 27001:2013
> > DIN EN ISO 9001:2015
> > DIN ISO/IEC 2-1:2011
> >
> > EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
> >
> > Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
> >
> > Disclaimer Privacy:
> > Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien)
> ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
> >
> > The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> >> Am 12.01.2020 um 07:17 schrieb Rohit Yadav :
> >>
> >> Hi PL,
> >>
> >> Thanks for 

Re: CloudStack Kubernetes provider containers on DockerHub

[Pierre-Luc Dion]

I remember why we did create our own org in dockerhub, it was to be able to
create multiple images for various parts of CloudStack such as marvin,
cloudmonkey, management-server, ...
Would we be able to decouple cloudstack easily inside the apache org ?

Going to wait before releasing the current orgs  "cloudstack" and
"apachecloudstack"(empty), there is no way to hide them but I don't want
someone outside of our community take those names.

Cheers,

On Thu, Jan 16, 2020 at 1:53 AM Rohit Yadav 
wrote:

> Hi Paul,
>
> I think we added the Dockerfile, I did not actually do anything else.
> Maybe there is a hook that automatically kicks to build and publish
> container images on the apache dockerhub org (
> https://hub.docker.com/r/apache/cloudstack-cloudmonkey). I'm also not
> part of the apache org on dockerhub.
>
> Maybe try adding a Dockerfile if an automatic integration already exists
> or ask asf-dev community?
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Paul Angus 
> Sent: Wednesday, January 15, 2020 22:30
> To: dev@cloudstack.apache.org ; Rohit Yadav <
> rohit.ya...@shapeblue.com>; Sven Vogel 
> Cc: Pierre-Luc Dion ; Will Stevens <
> wstev...@cloudops.com>; gabrasc...@gmail.com ; Wido
> den Hollander 
> Subject: RE: CloudStack Kubernetes provider containers on DockerHub
>
> Sorry folks, its been hectic...
>
> Yes Pierre-Luc, we should remove the non-Apache accounts.
>
> There is an /apache/cloudstack-cloudmonkey repository so it seems @Rohit
> Yadav knows how to get to upload to there @Sven Vogel
>
> I've been working on and off on docker files for building current
> simulator, as well as rpm/deb packaging images.  I was loosely planning to
> upload a current 'empty' simulator and a 'populated' simulator with
> multiple zones, accounts, VMs Networks, Firewall rules etc. It was with new
> UI development in mind.
>
> I was also thinking of a flow where we'd have automation where if there
> were any updates to the dockerfile we could press a button that would
> create and upload new build images.  An RM would be able to use the
> 'community' image to get a consistent outcome.
>
> Probably Feb before I can make them a polished reality.
>
> @Rohit Yadav can you share the process to get docker images pushed to
>
>
> Ever the optimist
>
> Paul.
>
>
>
> CTO
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
>
>
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Sven Vogel 
> Sent: 14 January 2020 15:47
> To: dev 
> Cc: Pierre-Luc Dion ; Will Stevens <
> wstev...@cloudops.com>; gabrasc...@gmail.com; Wido den Hollander <
> w...@widodh.nl>
> Subject: Re: CloudStack Kubernetes provider containers on DockerHub
>
> Hi Pierre, Hi Paul,
>
> @Paul do you know how we proceed. How we can get the space from Apache and
> align to the policy?
>
> Cheers
>
> Sven
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> s.vo...@ewerk.com
> www.ewerk.com<http://www.ewerk.com>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter
> Registergericht: Leipzig HRB 9065
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 2-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 13.01.2020 um 15:06 schrieb Pierre-Luc Dion :
> >
> 

Re: Issue with newest mysql-connector-java

[Pierre-Luc Dion]

Hi,

We got similar issue earlier this week, initial install on CentOS 7 does
seams to work, but downgrading mysql connector to latest 5.1.x version
worked.

On Tue, Jan 21, 2020 at 1:21 PM Sean Lair  wrote:

> Opened Issue:
> https://github.com/apache/cloudstack/issues/3826
>
> We noticed that on mysql-connector-java version 8.0.19 (not sure about
> other 8.0.x versions) we have errors such as the following:
>
> Caused by: java.lang.IllegalArgumentException: Can not set long field
> com.cloud.upgrade.dao.VersionVO.id to java.math.BigInteger
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
> at
> sun.reflect.UnsafeLongFieldAccessorImpl.set(UnsafeLongFieldAccessorImpl.java:102)
>
> Looks like in code we are using Long with Auto Increment fields, but the
> DB columns are actually BigInt.  Downgrading to the EPEL release of
> mysql-connector-java (5.1.25-3) fixed the issue.  However, I expect lots of
> people would hit this, because in the upgrade guides we specify to add the
> mysql-community repo - which uses newer mysql-connectors:
>
>
> http://docs.cloudstack.apache.org/projects/archived-cloudstack-release-notes/en/4.11/upgrade/upgrade-4.9.html
>
> Thanks
> Sean
>

Re: [DISCUSS] SIG for SDN Tungsten Fabric Network Plugin

[Pierre-Luc Dion]

That's a nice initiative and good timing, we will be interesting and
willing to contribute as well, if we go with tungsten Fabric.

We recently looked at using Contrail, the commercial version of Tungsten,
not very impressed for managing network switches to be honest.
Overcomplicated software with limited configuration schema for switches.
Although we haven't looked at the service orchestration part.
It seems to be somewhat  useful when it comes to orchestrate services such
as firewall, LB, vxlan routers,...
Will also be challenging to deal with their documentation which lacked a
bit and also their high integration to OpenStack :-(
We are expecting to have a close eye on Tungsten for our network services
evolution.

Perso, I would look for another SDN, but I'm not knowledgeable in this
topic at the moment, it might be the best open source option available at
the moment.

Cheers,


On Mon, Feb 3, 2020 at 11:51 AM Simon Weller 
wrote:

> All,
>
> During the 2019 CCC @ Apachecon North America, a few of us discussed the
> need for a new Software Defined Networking (SDN) integration for
> CloudStack, now that Nuage has chosen to depreciate their SDN product
> portfolio.
> I've been working closely with Sven Vogel on outlining how we might be
> able to start a Special Interest Group (SIG) to design and build an ACS
> network plugin into the Linux Foundation project Tungsten Fabric (Formally
> known as Open Contrail).
>
> Both Sven's company, EWERK and my company ENA are willing to contribute
> developers to this effort, as we feel it's important for Apache CloudStack
> to have a robust SDN option that utilizes a well known and stable open
> source SDN project and one that is community supported.
> Although there is an existing plugin for Contrail that was originally
> contributed by Juniper, it has been orphaned in the ACS code base for many
> years and to my knowledge, it’s unusable.
> Over the years, we've had a number of SDN integrations come and go. This
> has left users in the lurch and discouraged other potential companies from
> considering these options, as one has to be confident in the longevity of
> the plugin.
>
> Why Tungsten Fabric?
> Tungsten Fabric has been around for quite a while and it is now officially
> a Linux Foundation project, so it has a considerable amount of support
> behind it. It's scalable, multi-tenant, supports a number of advanced
> security features, as well a large chunk of built in components we
> currently need a Virtual Router to provide.
> It's dual stack IPV4 and IPV6 and heavily utilizes BGP and MPLS. This
> makes it ideal for those of us that maintain our own networks, as it will
> provide tight integration options and eliminate the need for complicated
> Private Gateway (PG) setups for VPCs.
> Additionally, with service stitching and EVPN capabilities, it will make
> it a lot easier for operators to support other platforms without having to
> build a dedicated plugin, or figure out how to support those network or
> security features through other L2/L3 hacks.
>
> Sven and I would like to gauge feedback from the community on this
> proposal and see whether other organizations are interested in
> participating.
>
> Thanks,
>
> Sven and Simon
>

Re: Whats new in 4.4

[Pierre-Luc Dion]

Should we consider all New Features from Jira with Fixed version of 4.4 or
only those that have Resolved Status for the Release Notes?

Also, Does 4.4 support new Guest OS  or hypervisor versions ?

Thanks,


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Apr 8, 2014 at 2:26 PM, Mike Tutkowski  wrote:

> Hi Hugo,
>
> For the 4.4 release, I extended managed storage to support a 1:1 mapping
> between a CloudStack root disk and a backend volume (in my case, a SAN
> volume) when using XenServer.
>
> This 1:1 mapping paves the way for enabling guaranteed QoS for root disks
> (I have the same support in place already for data disks for XenServer,
> VMware, and KVM).
>
> I have code in already to support this on VMware; however, I'm currently
> discovering VMware behavior that I didn't previously know existed (I've
> been talking with Kelven about this). Based on the results on our
> conversation, I'll know if it's a simple matter or not to patch up my
> VMware logic to support a 1:1 root-disk mapping in 4.4, as well (otherwise
> that will end up in 4.5). All of my VMware testing for this worked, but it
> was conducted with storage code running inside of the CS MS. I was unaware
> that this kind of storage-related code for VMware can also run inside of a
> SSVM.
>
> Thanks!
> Mike
>
>
> On Tue, Apr 8, 2014 at 11:18 AM, Hugo Trippaers  wrote:
>
> > Yes,
> >
> > It's going to be the input for the release notes. :-) I thought it would
> > be nice to ask everyone what should be in there.
> >
> > Thanks for the input!
> >
> > Cheers,
> >
> > Hugo
> >
> >
> > On 8 apr. 2014, at 11:16, Alena Prokharchyk <
> alena.prokharc...@citrix.com>
> > wrote:
> >
> > > Hugo, are you planning to post it online for the future reference once
> > you
> > > get the information? That would be great.
> > >
> > > From my side, following was checked in to 4.4:
> > >
> > > CLOUDSTACK-5870: API support for retrieving user data
> > >
> > > deployVm/startVm APIs: ability to define deploymentPlanner for
> VmToStart
> > > in the api call (available to ROOT admin only)
> > >
> > >
> > > -Alena.
> > >
> > > On 4/8/14, 9:50 AM, "Hugo Trippaers"  wrote:
> > >
> > >> Heya,
> > >>
> > >> I don¹t know so you tell me ;-)
> > >>
> > >> Seriously, i¹m looking for input on what the new things are that we
> > added
> > >> into 4.4. So if you have something that you think is worth mentioning
> > for
> > >> the 4.4 release, reply to this thread. It can be a completely new
> > >> feature, but i¹d be equally interested in fixed bugs or refactoring.
> > I¹ll
> > >> be combining this with the input from jira and review board, but i
> would
> > >> prefer to get this info directly from the people that actually worked
> on
> > >> the feature.
> > >>
> > >> Cheers,
> > >>
> > >> Hugo
> > >
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>

[DISCUSS] Release-notes changes

[Pierre-Luc Dion]

I did some changes on the release-note, rtd.org project that are ready for
a pull request.

I've change few things and I would like your input/vote on them:

- about.rst split into multiple files, fixed and known issues are on
separate files and list in main toctree
- use of .rst variables for Versions, release, url,
- use of [tag] on new features names
- all new features have a link to their functional Specs on the wiki, or
Jira issue. (ideally it would like to the official doc of the feature)

See online fork version: (this is not official URL)
http://cs-rn-test.readthedocs.org/en/latest/


Thanks,

Pierre-Luc Dion

Re: Whats new in 4.4

[Pierre-Luc Dion]

Hi,

Thanks Daan, I'll work something with this,

Tuna, is there a quick description / link to this new feature of
cloudstack, look to me like a very nice feature for CloudStack.




On Wed, May 14, 2014 at 5:23 AM, Nguyen Anh Tu  wrote:

> Hi,
>
> For 4.4, I push Autoscale without Netscaler feature. I'm on the way testing
> it.
>
> Cheers,
>
> --Tuna
>
>
> On Wed, May 14, 2014 at 8:51 AM, Pierre-Luc Dion 
> wrote:
>
> > Should we consider all New Features from Jira with Fixed version of 4.4
> or
> > only those that have Resolved Status for the Release Notes?
> >
> > Also, Does 4.4 support new Guest OS  or hypervisor versions ?
> >
> > Thanks,
> >
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 855-OK-CLOUD (855-652-5683) x1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
> > On Tue, Apr 8, 2014 at 2:26 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com
> > > wrote:
> >
> > > Hi Hugo,
> > >
> > > For the 4.4 release, I extended managed storage to support a 1:1
> mapping
> > > between a CloudStack root disk and a backend volume (in my case, a SAN
> > > volume) when using XenServer.
> > >
> > > This 1:1 mapping paves the way for enabling guaranteed QoS for root
> disks
> > > (I have the same support in place already for data disks for XenServer,
> > > VMware, and KVM).
> > >
> > > I have code in already to support this on VMware; however, I'm
> currently
> > > discovering VMware behavior that I didn't previously know existed (I've
> > > been talking with Kelven about this). Based on the results on our
> > > conversation, I'll know if it's a simple matter or not to patch up my
> > > VMware logic to support a 1:1 root-disk mapping in 4.4, as well
> > (otherwise
> > > that will end up in 4.5). All of my VMware testing for this worked, but
> > it
> > > was conducted with storage code running inside of the CS MS. I was
> > unaware
> > > that this kind of storage-related code for VMware can also run inside
> of
> > a
> > > SSVM.
> > >
> > > Thanks!
> > > Mike
> > >
> > >
> > > On Tue, Apr 8, 2014 at 11:18 AM, Hugo Trippaers 
> > wrote:
> > >
> > > > Yes,
> > > >
> > > > It's going to be the input for the release notes. :-) I thought it
> > would
> > > > be nice to ask everyone what should be in there.
> > > >
> > > > Thanks for the input!
> > > >
> > > > Cheers,
> > > >
> > > > Hugo
> > > >
> > > >
> > > > On 8 apr. 2014, at 11:16, Alena Prokharchyk <
> > > alena.prokharc...@citrix.com>
> > > > wrote:
> > > >
> > > > > Hugo, are you planning to post it online for the future reference
> > once
> > > > you
> > > > > get the information? That would be great.
> > > > >
> > > > > From my side, following was checked in to 4.4:
> > > > >
> > > > > CLOUDSTACK-5870: API support for retrieving user data
> > > > >
> > > > > deployVm/startVm APIs: ability to define deploymentPlanner for
> > > VmToStart
> > > > > in the api call (available to ROOT admin only)
> > > > >
> > > > >
> > > > > -Alena.
> > > > >
> > > > > On 4/8/14, 9:50 AM, "Hugo Trippaers"  wrote:
> > > > >
> > > > >> Heya,
> > > > >>
> > > > >> I don¹t know so you tell me ;-)
> > > > >>
> > > > >> Seriously, i¹m looking for input on what the new things are that
> we
> > > > added
> > > > >> into 4.4. So if you have something that you think is worth
> > mentioning
> > > > for
> > > > >> the 4.4 release, reply to this thread. It can be a completely new
> > > > >> feature, but i¹d be equally interested in fixed bugs or
> refactoring.
> > > > I¹ll
> > > > >> be combining this with the input from jira and review board, but i
> > > would
> > > > >> prefer to get this info directly from the people that actually
> > worked
> > > on
> > > > >> the feature.
> > > > >>
> > > > >> Cheers,
> > > > >>
> > > > >> Hugo
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > *(tm)*
> > >
> >
>

Release note of 4.3 questions

[Pierre-Luc Dion]

I have question about supported Hypervisor for the Release-notes

ref:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3/compat.html#supported-hypervisor-versions

1. Hyper-V is an hypervisor family so cloudstack now support 4 hypervisor
 family?
2. what's the difference between :

Windows Server 2012 R2 (with Hyper-V Role enabled)

Hyper-V 2012 R2
3. new API method: is there a way to know what are new API method added in
4.4 ?


Thanks,

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

[DISCUSSION] Release-notes format

[Pierre-Luc Dion]

I'm not sure if this would require a votes.

I've update the Upgrade instruction from 4.3 to 4.4 and I would like to
propose theses changes as part of 4.4 release note:

1. split upgrade instruction into separate files to facilitate edition

2.  add upgrade instructions in the main left menu  and use of title for
upgrade steps
 see this test :
http://cs44-rn-test.readthedocs.org/upgrade/upgrade-4.3.html

3. http://cs44-rn-test.readthedocs.org/upgrade/upgrade-4.3.html  is the
untested yet upgrade instruction, does anyone have any missing steps ?

4.  I've split Management-server instruction from KVM in ubuntu and rhel
instructions

5. Does HyperV require upgrade particular instruction ?



Pierre-Luc