Re: CCC Miami Sponsor: ShapeBlue

2017-02-02 Thread Will Stevens
Hey Raj,
Ya, it is a little hard to know for sure, but we are making a big push for
this conference.  The last one was just an ApacheCon we tried to have a
small presence at, and we had a VERY small presence (as you know).  This
time we are actually running a CCC at the event, so we are focusing on
getting a lot more of the community there for this event.

We would love for you to sponsor and for your team to submit talks.
Looking forward to seeing you there.  :)

Cheers,

Will

On Sun, Jan 29, 2017 at 9:37 PM, Rajesh Ramchandani <
rajesh.ramchand...@accelerite.com> wrote:

> Hi Will -
>
>
> I was wondering if you could suggest what will be the
> attendance expectation at CCC? I am hoping it will be a lot more than the
> ApacheCon Europe last year. We would love to sponsor as long as we are able
> to rally our community members to attend. Thanks.
>
>
> Raj
>
>
> --
> *From:* Will Stevens 
> *Sent:* Sunday, January 29, 2017 10:05 AM
> *To:* market...@cloudstack.apache.org; users@cloudstack.apache.org;
> d...@cloudstack.apache.org
> *Subject:* CCC Miami Sponsor: ShapeBlue
>
> Please join me in welcoming ShapeBlue  as the
> ShapeBlue - The CloudStack Company 
> www.shapeblue.com
> Introduction Upgrading CloudStack can sometimes be a little daunting - but
> as the 5P's proverb goes - Proper Planning Prevents Poor Performance.
>
>
> first official sponsor of the CloudStack Collaboration Conference in
> Miami.  ShapeBlue has been a dedicated sponsor and Apache CloudStack
> supporter and we are thrilled to have them on board for this event.
>
> The CloudStack Collaboration Conference in Miami is being hosted by
> ApacheCon and it is shaping up to be a great event.  We are all looking
> forward to seeing you there.
>
> If you would like more information about the event, please checkout the
> event website: http://us.cloudstackcollab.org/
> Apache CloudStack Collaboration Conference - USA
> 
> us.cloudstackcollab.org
> Apache CloudStack Collaboration Conference hosted in Miami at ApacheCon.
>
>
>
> If you are interested in sponsoring the event, please review the
> sponsorship section: http://us.cloudstackcollab.org/#sponsors
> Apache CloudStack Collaboration Conference - USA
> 
> us.cloudstackcollab.org
> Apache CloudStack Collaboration Conference hosted in Miami at ApacheCon.
>
>
>
> Thanks again for the support ShapeBlue and looking forward to seeing you at
> the event.
>
> Cheers,
>
> Will Stevens
> VP @ Apache CloudStack
>
> 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.
>


AW: Issues upgrading to XenServer 7

2017-02-02 Thread S . Brüseke - proIO GmbH
Hi Martin,

here are my 2 cents:
we do not upgrade XenServer in our CS installation at all. What we do is to 
move all VMs from one host, eject it from the pool and delete it from CS. After 
that we are doing a fresh installation of XenServer, create a new pool and add 
this pool as new cluster to CS. Then we move VMs via live migration from the 
old cluster to the new one so we end up in the next free XenServer in the old 
pool to eject it and so on.

Mit freundlichen Grüßen / With kind regards,

Swen


-Ursprüngliche Nachricht-
Von: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Gesendet: Donnerstag, 2. Februar 2017 15:15
An: users@cloudstack.apache.org
Betreff: Re: Issues upgrading to XenServer 7

Hi Martin

Check 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/hypervisor/xenserver.html#upgrading-xenserver-versions


Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 02/02/2017, 13:09, "Martin Emrich"  wrote:

Hi!,

After getting the upgrade to 4.9.2.0 on my test cloud going, I decided to 
upgrade the hosts from XenServer 6.5SP1 to XenServer 7. I followed the process 
like I did many times with upgrades form 6.0 to 6.2 or to 6.5.
Normally, Cloudstack "reinstalled" the integration scripts under /opt/cloud 
after upgrading a XenServer, I usually can watch it In the logs while it copies 
scripts and stuff to the XenServers.

But this time, they do not appear, and the host stays in the Alert state.

In the log, I see:

2017-02-02 14:07:07,431 DEBUG [c.c.h.Status] (AgentTaskPool-6:ctx-3c41c4cd) 
(logid:47da929b) Transition:[Resource state = Enabled, Agent event = 
AgentDisconnected, Host id = 2, name = cdsdev-xen5]
2017-02-02 14:07:07,434 WARN  [c.c.r.ResourceManagerImpl] 
(AgentTaskPool-5:ctx-f768a3d8) (logid:aefd7fd0) Unable to connect due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at 
com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:627)
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:564)
at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1518)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1902)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:2035)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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 
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.$Proxy161.createHostAndAgent(Unknown Source)
at 
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.runInContext(AgentManagerImpl.java:1135)
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 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

How can I motivate CloudStack to install the agent/scripts on the 
XenServers? Or can I do it manually?

Thanks,

Martin




dag.sonst...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918

AW: Issues upgrading to XenServer 7

2017-02-02 Thread Martin Emrich
Hey Dag,

awesome! Apparently I skipped clearing the host tags, obviously that indicates 
to ACS whether the integration scripts are already in place.
Shortly after clearing them, the scripts were deployed and the hosts are coming 
up now.

Thanks,

Martin

-Ursprüngliche Nachricht-
Von: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Gesendet: Donnerstag, 2. Februar 2017 15:15
An: users@cloudstack.apache.org
Betreff: Re: Issues upgrading to XenServer 7

Hi Martin

Check 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/hypervisor/xenserver.html#upgrading-xenserver-versions


Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 02/02/2017, 13:09, "Martin Emrich"  wrote:

Hi!,

After getting the upgrade to 4.9.2.0 on my test cloud going, I decided to 
upgrade the hosts from XenServer 6.5SP1 to XenServer 7. I followed the process 
like I did many times with upgrades form 6.0 to 6.2 or to 6.5.
Normally, Cloudstack "reinstalled" the integration scripts under /opt/cloud 
after upgrading a XenServer, I usually can watch it In the logs while it copies 
scripts and stuff to the XenServers.

But this time, they do not appear, and the host stays in the Alert state.

In the log, I see:

2017-02-02 14:07:07,431 DEBUG [c.c.h.Status] (AgentTaskPool-6:ctx-3c41c4cd) 
(logid:47da929b) Transition:[Resource state = Enabled, Agent event = 
AgentDisconnected, Host id = 2, name = cdsdev-xen5]
2017-02-02 14:07:07,434 WARN  [c.c.r.ResourceManagerImpl] 
(AgentTaskPool-5:ctx-f768a3d8) (logid:aefd7fd0) Unable to connect due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at 
com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:627)
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:564)
at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1518)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1902)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:2035)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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 
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.$Proxy161.createHostAndAgent(Unknown Source)
at 
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.runInContext(AgentManagerImpl.java:1135)
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 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

How can I motivate CloudStack to install the agent/scripts on the 
XenServers? Or can I do it manually?

Thanks,

Martin




dag.sonst...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 



Re: Issues upgrading to XenServer 7

2017-02-02 Thread Dag Sonstebo
Hi Martin

Check 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/hypervisor/xenserver.html#upgrading-xenserver-versions


Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 02/02/2017, 13:09, "Martin Emrich"  wrote:

Hi!,

After getting the upgrade to 4.9.2.0 on my test cloud going, I decided to 
upgrade the hosts from XenServer 6.5SP1 to XenServer 7. I followed the process 
like I did many times with upgrades form 6.0 to 6.2 or to 6.5.
Normally, Cloudstack "reinstalled" the integration scripts under /opt/cloud 
after upgrading a XenServer, I usually can watch it In the logs while it copies 
scripts and stuff to the XenServers.

But this time, they do not appear, and the host stays in the Alert state.

In the log, I see:

2017-02-02 14:07:07,431 DEBUG [c.c.h.Status] (AgentTaskPool-6:ctx-3c41c4cd) 
(logid:47da929b) Transition:[Resource state = Enabled, Agent event = 
AgentDisconnected, Host id = 2, name = cdsdev-xen5]
2017-02-02 14:07:07,434 WARN  [c.c.r.ResourceManagerImpl] 
(AgentTaskPool-5:ctx-f768a3d8) (logid:aefd7fd0) Unable to connect due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at 
com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:627)
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:564)
at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1518)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1902)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:2035)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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 
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.$Proxy161.createHostAndAgent(Unknown Source)
at 
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.runInContext(AgentManagerImpl.java:1135)
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 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

How can I motivate CloudStack to install the agent/scripts on the 
XenServers? Or can I do it manually?

Thanks,

Martin




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 



Issues upgrading to XenServer 7

2017-02-02 Thread Martin Emrich
Hi!,

After getting the upgrade to 4.9.2.0 on my test cloud going, I decided to 
upgrade the hosts from XenServer 6.5SP1 to XenServer 7. I followed the process 
like I did many times with upgrades form 6.0 to 6.2 or to 6.5.
Normally, Cloudstack "reinstalled" the integration scripts under /opt/cloud 
after upgrading a XenServer, I usually can watch it In the logs while it copies 
scripts and stuff to the XenServers.

But this time, they do not appear, and the host stays in the Alert state.

In the log, I see:

2017-02-02 14:07:07,431 DEBUG [c.c.h.Status] (AgentTaskPool-6:ctx-3c41c4cd) 
(logid:47da929b) Transition:[Resource state = Enabled, Agent event = 
AgentDisconnected, Host id = 2, name = cdsdev-xen5]
2017-02-02 14:07:07,434 WARN  [c.c.r.ResourceManagerImpl] 
(AgentTaskPool-5:ctx-f768a3d8) (logid:aefd7fd0) Unable to connect due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at 
com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:627)
at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:564)
at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1518)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1902)
at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:2035)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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 
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.$Proxy161.createHostAndAgent(Unknown Source)
at 
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.runInContext(AgentManagerImpl.java:1135)
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 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

How can I motivate CloudStack to install the agent/scripts on the XenServers? 
Or can I do it manually?

Thanks,

Martin