Re: Remove 'md5Hashed' variable from Javascript

[Gabriel Beims Bräscher]

+1

2018-04-12 20:35 GMT-03:00 Rohit Yadav :

> +1
>
>
>
> - Rohit
>
> 
>
>
>
> 
> From: Rafael Weingärtner 
> Sent: Friday, April 13, 2018 4:04:24 AM
> To: users; dev
> Subject: Re: Remove 'md5Hashed' variable from Javascript
>
> Hello folks,
> I have not heard anything back here. I will still wait a few more days. If
> I do not see anybody against it, I will assume lazy consensus and proceed
> removing these variables.
>
> On Mon, Apr 9, 2018 at 2:31 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Hello fellow CloudStackers,
> >
> > Today I was working on CLOUDSTACK-5235, which is a security issue, and I
> > noticed a variable ‘md5Hashed’ in the javascript that does not seem to be
> > useful at all. This variable was used to control if we hash or not the
> > password of users in the user side (browser). However, we no longer hash
> > the password on the user side. All of the password processing is executed
> > in the server side according to the priority of hashing mechanism defined
> > by the administrator.
> >
> > I am addressing this cleanup with this PR https://github.com/apache/
> > cloudstack/pull/2555.
> >
> > If you have any objections regarding this variable and its relate code
> > removal, please do so. Otherwise, we will proceed to remove it.
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: Remove 'md5Hashed' variable from Javascript

[Rohit Yadav]

+1



- Rohit






From: Rafael Weingärtner 
Sent: Friday, April 13, 2018 4:04:24 AM
To: users; dev
Subject: Re: Remove 'md5Hashed' variable from Javascript

Hello folks,
I have not heard anything back here. I will still wait a few more days. If
I do not see anybody against it, I will assume lazy consensus and proceed
removing these variables.

On Mon, Apr 9, 2018 at 2:31 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Hello fellow CloudStackers,
>
> Today I was working on CLOUDSTACK-5235, which is a security issue, and I
> noticed a variable ‘md5Hashed’ in the javascript that does not seem to be
> useful at all. This variable was used to control if we hash or not the
> password of users in the user side (browser). However, we no longer hash
> the password on the user side. All of the password processing is executed
> in the server side according to the priority of hashing mechanism defined
> by the administrator.
>
> I am addressing this cleanup with this PR https://github.com/apache/
> cloudstack/pull/2555.
>
> If you have any objections regarding this variable and its relate code
> removal, please do so. Otherwise, we will proceed to remove it.
>
> --
> Rafael Weingärtner
>



--
Rafael Weingärtner

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[Solved] Re: PV vs HVM guest on XenServer 7.0

[Yiping Zhang]

After more investigation, I found out that  changing template's "OS Type" 
assignment affects how a VM is started as PV or HVM guest on either XenServer 
6.5 or 7.0 clusters:

On XenServer 6.5 clusters,  64 bit RHEL guests with versions up to 6.7 (last 
6.x version listed by ACS 4.9.3.0) are always started as PV guest, and they all 
run properly.
On XenServer 7.0 clusters,  64 bit RHEL guests with versions up to 6.4 are 
started as PV guests and run properly, guests with version 6.5 onwards are 
started as HVM guest, and these won't start.

So, the simple work around is to assign "RHEL 6.4 (64bit)" to all my rhel 6.x 
templates so that guests using these templates are always started as PV guest 
regardless the version of XenServer cluster they are running on.  

IMHO, I think this is a bug in CloudStack, that is all rhel 6.x guests should 
be started as PV guests regardless Xen hypervisor versions (I only verified on 
XenServer 6.5 and 7.0).

Yiping

On 4/11/18, 2:31 PM, "Yiping Zhang"  wrote:

Hi, list:


I am in the process of upgrading my hypervisors clusters from XenServer 6.5 
to 7.0 for all my ACS instances.

My XS 7.0 clusters are patched up to XS70E050.

During cluster rolling upgrade, VM instances are live migrated several 
times, eventually all of them running on XS 7.0 hosts.
However, out of a hundred or so instances, a few of rhle 6.x VM got stuck 
at “Plex86/Bochs VGABios …” screen with at least one vCPU at 100%.
Comparing VM parameters between running and stuck instances, I can see that 
running instances are PV guests while stuck instances are HVM guests.
RHEL 7.x guest are always in HVM mode and always runs on both XS 6.5 and 
7.0 hosts.

Running RHEL6.x guests:

   HVM-boot-policy ( RW):

   HVM-boot-params (MRW):

 HVM-shadow-multiplier ( RW): 1.000

   PV-args ( RW): graphical utf8

 PV-bootloader ( RW): pygrub

Stuck RHEL 6.x guests:

   HVM-boot-policy ( RW): BIOS order

   HVM-boot-params (MRW): order: dc

 HVM-shadow-multiplier ( RW): 1.000

   PV-args ( RW):

 PV-bootloader ( RW):

Why does CloudStack convert just a few rhel 6.x instances into HVM mode, 
while leaving most in PV mode?
How would I force them back to PV guests?

Thanks for all the help

Yiping

Re: Remove 'md5Hashed' variable from Javascript

[Rafael Weingärtner]

Hello folks,
I have not heard anything back here. I will still wait a few more days. If
I do not see anybody against it, I will assume lazy consensus and proceed
removing these variables.

On Mon, Apr 9, 2018 at 2:31 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Hello fellow CloudStackers,
>
> Today I was working on CLOUDSTACK-5235, which is a security issue, and I
> noticed a variable ‘md5Hashed’ in the javascript that does not seem to be
> useful at all. This variable was used to control if we hash or not the
> password of users in the user side (browser). However, we no longer hash
> the password on the user side. All of the password processing is executed
> in the server side according to the priority of hashing mechanism defined
> by the administrator.
>
> I am addressing this cleanup with this PR https://github.com/apache/
> cloudstack/pull/2555.
>
> If you have any objections regarding this variable and its relate code
> removal, please do so. Otherwise, we will proceed to remove it.
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

RE: CS 4.11 : Error display fresh install

[Paul Angus]

Also, what database server and version are you using please?

From: Rohit Yadav 
Sent: 12 April 2018 12:01
To: users@cloudstack.apache.org; olivier.g...@ariasnet.com
Subject: Re: CS 4.11 : Error display fresh install


Hi Olivier,



Can you ensure that host_view is created? If not run the CREATE view from here:

https://github.com/apache/cloudstack/blob/4.11/engine/schema/resources/META-INF/db/schema-41000to41100.sql#L158

After that please report if you're able to see any hosts?



Can you share details of your management server host (distro, version etc) and 
if you performed any in-place upgrade? Also share output of:

find /usr/share/cloudstack-management/ | grep schema





- Rohit



rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue





From: Olivier GUIN >
Sent: Monday, March 26, 2018 4:01:09 PM
To: users@cloudstack.apache.org
Subject: Re: CS 4.11 : Error display fresh install

Hi Rohit,

Answers is blue !
My host_view is empty !

Regards,
Olivier

Le 26/03/2018 à 04:05, Rohit Yadav a écrit :

Olivier,





Can you share the sql outputs of:





use cloud;



select * from version;

MariaDB [cloud]> select * from version;

++--+-+--+

| id | version  | updated | step |

++--+-+--+

|  4 | 4.0.0| 2018-03-24 10:50:03 | Complete |

|  6 | 4.1.0| 2018-03-24 13:52:43 | Complete |

|  8 | 4.2.0| 2018-03-24 13:54:04 | Complete |

| 10 | 4.2.1| 2018-03-24 13:54:04 | Complete |

| 12 | 4.3.0| 2018-03-24 13:54:38 | Complete |

| 14 | 4.4.0| 2018-03-24 13:57:10 | Complete |

| 16 | 4.4.1| 2018-03-24 13:57:11 | Complete |

| 18 | 4.4.2| 2018-03-24 13:57:11 | Complete |

| 20 | 4.5.0| 2018-03-24 13:57:19 | Complete |

| 22 | 4.5.1| 2018-03-24 13:57:19 | Complete |

| 24 | 4.5.2| 2018-03-24 13:57:19 | Complete |

| 26 | 4.6.0| 2018-03-24 13:57:21 | Complete |

| 28 | 4.6.1| 2018-03-24 13:57:21 | Complete |

| 30 | 4.7.0| 2018-03-24 13:57:24 | Complete |

| 32 | 4.7.1| 2018-03-24 13:57:24 | Complete |

| 34 | 4.8.0| 2018-03-24 13:57:25 | Complete |

| 36 | 4.8.1| 2018-03-24 13:57:25 | Complete |

| 38 | 4.9.0| 2018-03-24 13:57:27 | Complete |

| 42 | 4.9.1.0  | 2018-03-24 13:57:29 | Complete |

| 44 | 4.9.2.0  | 2018-03-24 13:57:29 | Complete |

| 46 | 4.9.3.0  | 2018-03-24 13:57:29 | Complete |

| 48 | 4.10.0.0 | 2018-03-24 13:57:38 | Complete |

| 50 | 4.11.0.0 | 2018-03-24 13:57:46 | Complete |

++--+-+--+

23 rows in set (0.00 sec)





select * from host\G;

MariaDB [cloud]> select * from host\G;

*** 1. row ***

   id: 4

 name: cc-1.wayscom.com

 uuid: 8b94bdb7-ac5d-4fa2-81be-df1869248e7c

   status: Up

 type: Routing

   private_ip_address: 172.16.11.11

  private_netmask: 255.255.255.0

  private_mac_address: e4:1f:13:b9:cc:5c

   storage_ip_address: 172.16.6.11

  storage_netmask: 255.255.255.0

  storage_mac_address: fe:ff:ff:ff:ff:ff

 storage_ip_address_2: NULL

storage_mac_address_2: NULL

storage_netmask_2: NULL

   cluster_id: 4

public_ip_address: 172.16.11.11

   public_netmask: 255.255.255.0

   public_mac_address: e4:1f:13:b9:cc:5c

   proxy_port: NULL

   data_center_id: 4

   pod_id: 4

  cpu_sockets: 2

 cpus: 16

speed: 2400

  url: iqn.2016-12.com.example:09bd3e90

  fs_type: NULL

  hypervisor_type: XenServer

   hypervisor_version: 6.5.0

  ram: 62269760512

 resource: 
com.cloud.hypervisor.xenserver.resource.XenServer650Resource

  version: 4.11.0.0

   parent: NULL

   total_size: NULL

 capabilities: xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 , 
hvm-3.0-x86_32p , hvm-3.0-x86_64

 guid: b2bdaefb-f347-43f9-af9f-d5c2cf561c9c

available: 1

setup: 1

  dom0_memory: 0

last_ping: 1486231189

   mgmt_server_id: 52228986878

 disconnected: NULL

  created: 2018-03-24 14:16:33

  removed: NULL

 update_count: 2

   resource_state: Enabled

owner: NULL

  lastUpdated: NULL

 engine_state: Disabled

*** 2. row ***

   id: 8

 name: v-1-VM

 uuid: 8f92a79b-31cf-426a-846d-5fc16ee3862d

   status: Up

 type: ConsoleProxy

   private_ip_address: 172.16.11.189

  private_netmask: 

Re: Upgrade from ACS 4.9.3 to 4.11.0

[Rohit Yadav]

Hi Andrei,


Thanks for sharing, yes the egress thing is a known issue which is caused due 
to failure during VR setup to create egress table. By performing a restart of 
the network (without cleanup option selected), the egress table gets created 
and rules are successfully applied.


The issue has been fixed in the vr downtime pr:

https://github.com/apache/cloudstack/pull/2508


- Rohit






From: Andrei Mikhailovsky 
Sent: Tuesday, April 3, 2018 3:33:43 PM
To: users
Subject: Re: Upgrade from ACS 4.9.3 to 4.11.0

Rohit,

Following the update from 4.9.3 to 4.11.0, I would like to comment on a few 
things:

1. The upgrade went well, a part from the cloudstack-management server startup 
issue that I've described in my previous email.
2. there was an issue with the virtual router template upgrade. The issue is 
described below:

VR template upgrade issue:

After updating the systemvm template I went onto the Infrastructure > Virtual 
Routers and selected the Update template option for each virtual router. The 
virtual routers were updated successfully using the new templates. However, 
this has broken ALL Egress rules on all networks and none of the guest vms. 
Port forwarding / incoming rules were working just fine. Removal and addition 
of Egress rules did not fix the issue. To fix the issue I had to restart each 
of the networks with the Clean up option ticked.


Cheers

Andrei

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

- Original Message -
> From: "Andrei Mikhailovsky" 
> To: "users" 
> Sent: Monday, 2 April, 2018 21:44:27
> Subject: Re: Upgrade from ACS 4.9.3 to 4.11.0

> Hi Rohit,
>
> Following some further investigation it seems that the installation packages
> replaced the following file:
>
> /etc/default/cloudstack-management
>
> with
>
> /etc/default/cloudstack-management.dpkg-dist
>
>
> Thus, the management server couldn't load the env variables and thus was 
> unable
> to start.
>
> I've put the file back and the management server is able to start.
>
> I will let you know if there are any other issues/problems.
>
> Cheers
>
> Andrei
>
>
>
> - Original Message -
>> From: "Andrei Mikhailovsky" 
>> To: "users" 
>> Sent: Monday, 2 April, 2018 20:58:59
>> Subject: Re: Upgrade from ACS 4.9.3 to 4.11.0
>
>> Hi Rohit,
>>
>> I have just upgraded and having issues starting the service with the 
>> following
>> error:
>>
>>
>> Apr 02 20:56:37 ais-cloudhost13 systemd[1]: cloudstack-management.service:
>> Failed to load environment files: No such file or directory
>> Apr 02 20:56:37 ais-cloudhost13 systemd[1]: cloudstack-management.service:
>> Failed to run 'start-pre' task: No such file or directory
>> Apr 02 20:56:37 ais-cloudhost13 systemd[1]: Failed to start CloudStack
>> Management Server.
>> -- Subject: Unit cloudstack-management.service has failed
>> -- Defined-By: systemd
>>
>> Cheers
>>
>> Andrei
>>
>> - Original Message -
>>> From: "Rohit Yadav" 
>>> To: "users" 
>>> Sent: Friday, 30 March, 2018 19:17:48
>>> Subject: Re: Upgrade from ACS 4.9.3 to 4.11.0
>>
>>> Some of the upgrade and minor issues have been fixed and will make their way
>>> into 4.11.1.0. You're welcome to upgrade and share your feedback, but bear 
>>> in
>>> mind due to some changes a new/updated systemvmtemplate need to be issued 
>>> for
>>> 4.11.1.0 (it will be compatible for both 4.11.0.0 and 4.11.1.0 releases, but
>>> 4.11.0.0 users will have to register that new template).
>>>
>>>
>>>
>>> - Rohit
>>>
>>> 
>>>
>>>
>>>
>>> 
>>> From: Andrei Mikhailovsky 
>>> Sent: Friday, March 30, 2018 11:00:34 PM
>>> To: users
>>> Subject: Upgrade from ACS 4.9.3 to 4.11.0
>>>
>>> Hello,
>>>
>>> My current infrastructure is ACS 4.9.3 with KVM based on Ubuntu 16.04 
>>> servers
>>> for the KVM hosts and the management server.
>>>
>>> I am planning to perform an upgrade from ACS 4.9.3 to 4.11.0 and was 
>>> wondering
>>> if anyone had any issues during the upgrades? Anything to watch out for?
>>>
>>> I have previously seen issues with upgrading to 4.10, which required some 
>>> manual
>>> db updates from what I recall. Has this issue been fixed in the 4.11 upgrade
>>> process?
>>>
>>> thanks
>>>
>>> Andrei
>>>
>>> rohit.ya...@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > @shapeblue

Re: SSL authentication failure

[Rohit Yadav]

Swastik - does your KVM host have ipmi capabilities, please refer to admin docs 
on using out-of-band management for host. You'll need to configure oobm 
configuration for a host in order to use them.



- Rohit






From: Swastik Mittal 
Sent: Tuesday, April 3, 2018 12:24:26 PM
To: users@cloudstack.apache.org
Subject: Re: SSL authentication failure

Forget to mention. On issuing an action for out of band management I get:

Out-of-band Management action (RESET) on host
(b7a92936-1ce9-4c90-aca3-6ea492bf028d) failed with error: Get Auth
Capabilities error Error issuing Get Channel Authentication Capabilies
request Error: Unable to establish IPMI v2 / RMCP+ session

On 4/3/18, Swastik Mittal  wrote:
> Hey Rohit,
>
> (in one-way ssl mode)
>
> The host has been added but the power state is disabled as out of band
> management is disabled. On enabling I get unknown state, but system vm's
> still show status running and agent state is marked by '-'.
>
> Where are the system VM's running if no agent state is detected?
>
> Also my console does not run but I can ssh into my ssvm. There is no
> ssvm-check file available. I think it is because system VM's are not
> correctly configured. So how do I power ON my host so that I get an agent
> state in system VM?
>
> regards
> Swastik
>
> On Tue, Apr 3, 2018 at 10:32 AM, Swastik Mittal 
> wrote:
>
>> Hey Rohit,
>>
>> I set my ca.plugin.root.auth.strictness to false and restarted all the
>> services and one way ssl works fine. But how do I solve the bug in case I
>> need to enable two way ssl.
>>
>> regards
>> Swastik
>>
>> On Tue, Apr 3, 2018 at 9:21 AM, Swastik Mittal 
>> wrote:
>>
>>> Hey Rohit
>>>
>>> I was installing a fresh enviroment. Added the host through command
>>> cloudstack-setup-agent, here it mentions everything done correctly but
>>> the host doesn't get added. (KVM host)
>>>
>>> Agent log file gives:
>>>
>>> 2018-04-03 09:12:14,584 INFO  [cloud.agent.Agent] (main:null) (logid:)
>>> Connecting to host:localhost
>>> 2018-04-03 09:12:14,584 INFO  [utils.nio.NioClient] (main:null)
>>> (logid:) Connecting to localhost:8250
>>> 2018-04-03 09:12:14,585 INFO  [utils.nio.Link] (main:null) (logid:)
>>> Conf file found: /etc/cloudstack/agent/agent.properties
>>> 2018-04-03 09:12:14,585 WARN  [utils.nio.Link] (main:null) (logid:)
>>> Failed to load keystore, using trust all manager
>>> 2018-04-03 09:12:14,589 ERROR [utils.nio.Link] (main:null) (logid:)
>>> SSL error caught during unwrap data: Unrecognized SSL message,
>>> plaintext connection?, for local address=/127.0.0.1:39863, remote
>>> address=localhost/127.0.0.1:8250. The client may have invalid
>>> ca-certificates.
>>> 2018-04-03 09:12:14,589 ERROR [utils.nio.NioClient] (main:null)
>>> (logid:) SSL Handshake failed while connecting to host: localhost
>>> port: 8250
>>> 2018-04-03 09:12:14,589 ERROR [utils.nio.NioConnection] (main:null)
>>> (logid:) Unable to initialize the threads.
>>> java.io.IOException: SSL Handshake failed while connecting to host:
>>> localhost port: 8250
>>> at com.cloud.utils.nio.NioClient.init(NioClient.java:67)
>>> at
>>> com.cloud.utils.nio.NioConnection.start(NioConnection.java:95)
>>> at com.cloud.agent.Agent.start(Agent.java:263)
>>> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:410)
>>> at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShe
>>> ll.java:378)
>>> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:362)
>>> at com.cloud.agent.AgentShell.start(AgentShell.java:467)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.apache.commons.daemon.support.DaemonLoader.start(DaemonL
>>> oader.java:243)
>>> 2018-04-03 09:12:14,590 INFO  [utils.exception.CSExceptionErrorCode]
>>> (main:null) (logid:) Could not find exception:
>>> com.cloud.utils.exception.NioConnectionException in error code list
>>> for exceptions
>>> 2018-04-03 09:12:14,590 WARN  [cloud.agent.Agent] (main:null) (logid:)
>>> NIO Connection Exception
>>> com.cloud.utils.exception.NioConnectionException: SSL Handshake failed
>>> while connecting to host: localhost port: 8250
>>> 2018-04-03 09:12:14,590 INFO  [cloud.agent.Agent] (main:null) (logid:)
>>> Attempted to connect to the server, but received an unexpected
>>> exception, trying again...
>>>
>>> While connecting through UI it gives authentication error.
>>>
>>> I also set ssh and sshd ports to 8250 and was able to ssh into
>>> management from host through it but still getting the same error while
>>> adding 

Re: CS 4.11 : Error display fresh install

[Rohit Yadav]

Hi Olivier,


Can you ensure that host_view is created? If not run the CREATE view from here:

https://github.com/apache/cloudstack/blob/4.11/engine/schema/resources/META-INF/db/schema-41000to41100.sql#L158


After that please report if you're able to see any hosts?


Can you share details of your management server host (distro, version etc) and 
if you performed any in-place upgrade? Also share output of:

find /usr/share/cloudstack-management/ | grep schema



- Rohit






From: Olivier GUIN 
Sent: Monday, March 26, 2018 4:01:09 PM
To: users@cloudstack.apache.org
Subject: Re: CS 4.11 : Error display fresh install

Hi Rohit,

Answers is blue !
My host_view is empty !

Regards,
Olivier

Le 26/03/2018 à 04:05, Rohit Yadav a écrit :

Olivier,


Can you share the sql outputs of:


use cloud;

select * from version;
MariaDB [cloud]> select * from version;
++--+-+--+
| id | version  | updated | step |
++--+-+--+
|  4 | 4.0.0| 2018-03-24 10:50:03 | Complete |
|  6 | 4.1.0| 2018-03-24 13:52:43 | Complete |
|  8 | 4.2.0| 2018-03-24 13:54:04 | Complete |
| 10 | 4.2.1| 2018-03-24 13:54:04 | Complete |
| 12 | 4.3.0| 2018-03-24 13:54:38 | Complete |
| 14 | 4.4.0| 2018-03-24 13:57:10 | Complete |
| 16 | 4.4.1| 2018-03-24 13:57:11 | Complete |
| 18 | 4.4.2| 2018-03-24 13:57:11 | Complete |
| 20 | 4.5.0| 2018-03-24 13:57:19 | Complete |
| 22 | 4.5.1| 2018-03-24 13:57:19 | Complete |
| 24 | 4.5.2| 2018-03-24 13:57:19 | Complete |
| 26 | 4.6.0| 2018-03-24 13:57:21 | Complete |
| 28 | 4.6.1| 2018-03-24 13:57:21 | Complete |
| 30 | 4.7.0| 2018-03-24 13:57:24 | Complete |
| 32 | 4.7.1| 2018-03-24 13:57:24 | Complete |
| 34 | 4.8.0| 2018-03-24 13:57:25 | Complete |
| 36 | 4.8.1| 2018-03-24 13:57:25 | Complete |
| 38 | 4.9.0| 2018-03-24 13:57:27 | Complete |
| 42 | 4.9.1.0  | 2018-03-24 13:57:29 | Complete |
| 44 | 4.9.2.0  | 2018-03-24 13:57:29 | Complete |
| 46 | 4.9.3.0  | 2018-03-24 13:57:29 | Complete |
| 48 | 4.10.0.0 | 2018-03-24 13:57:38 | Complete |
| 50 | 4.11.0.0 | 2018-03-24 13:57:46 | Complete |
++--+-+--+
23 rows in set (0.00 sec)


select * from host\G;
MariaDB [cloud]> select * from host\G;
*** 1. row ***
   id: 4
 name: cc-1.wayscom.com
 uuid: 8b94bdb7-ac5d-4fa2-81be-df1869248e7c
   status: Up
 type: Routing
   private_ip_address: 172.16.11.11
  private_netmask: 255.255.255.0
  private_mac_address: e4:1f:13:b9:cc:5c
   storage_ip_address: 172.16.6.11
  storage_netmask: 255.255.255.0
  storage_mac_address: fe:ff:ff:ff:ff:ff
 storage_ip_address_2: NULL
storage_mac_address_2: NULL
storage_netmask_2: NULL
   cluster_id: 4
public_ip_address: 172.16.11.11
   public_netmask: 255.255.255.0
   public_mac_address: e4:1f:13:b9:cc:5c
   proxy_port: NULL
   data_center_id: 4
   pod_id: 4
  cpu_sockets: 2
 cpus: 16
speed: 2400
  url: iqn.2016-12.com.example:09bd3e90
  fs_type: NULL
  hypervisor_type: XenServer
   hypervisor_version: 6.5.0
  ram: 62269760512
 resource: 
com.cloud.hypervisor.xenserver.resource.XenServer650Resource
  version: 4.11.0.0
   parent: NULL
   total_size: NULL
 capabilities: xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 , 
hvm-3.0-x86_32p , hvm-3.0-x86_64
 guid: b2bdaefb-f347-43f9-af9f-d5c2cf561c9c
available: 1
setup: 1
  dom0_memory: 0
last_ping: 1486231189
   mgmt_server_id: 52228986878
 disconnected: NULL
  created: 2018-03-24 14:16:33
  removed: NULL
 update_count: 2
   resource_state: Enabled
owner: NULL
  lastUpdated: NULL
 engine_state: Disabled
*** 2. row ***
   id: 8
 name: v-1-VM
 uuid: 8f92a79b-31cf-426a-846d-5fc16ee3862d
   status: Up
 type: ConsoleProxy
   private_ip_address: 172.16.11.189
  private_netmask: 255.255.255.0
  private_mac_address: 1e:00:1b:00:00:28
   storage_ip_address: 172.16.11.189
  storage_netmask: 255.255.255.0
  storage_mac_address: 1e:00:1b:00:00:28
 storage_ip_address_2: NULL
storage_mac_address_2: NULL
storage_netmask_2: NULL
   cluster_id: NULL
public_ip_address: 200.13.142.250
   public_netmask: 255.255.255.0
   public_mac_address: 1e:00:31:00:01:5f
   proxy_port: NULL
   data_center_id: 4
   pod_id: 4
  cpu_sockets: NULL

RE: ssvm NFS public ip

[Nicolas Bouige]

Hello All,

With this new deployement my ssvm is now okay.
I saw my mistake...the URLs were good for mgmt and systemvm template...but not 
for the cloudstack-agent installed on KVM...

Best regards,

N.B

-Message d'origine-
De : Nicolas Bouige [mailto:n.bou...@dimsi.fr] 
Envoyé : jeudi 12 avril 2018 09:56
À : users@cloudstack.apache.org
Objet : RE: ssvm NFS public ip

Hi Paul,

I used repository from shapeblue for mgmt-server and systemvm-template.
Im going to make a new fresh install (again :/) and double check the URL.

Thanks,

Best regards,
N.B


-Message d'origine-
De : Paul Angus [mailto:paul.an...@shapeblue.com] Envoyé : jeudi 12 avril 2018 
09:12 À : users@cloudstack.apache.org Objet : RE: ssvm NFS public ip

Hi Nicolas, this usually happens if you mix redist and noredist builds of mgmt. 
server and system vm code.

What URLs did you use for the management server repo and the system VM 
templates?



paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 


-Original Message-
From: Nicolas Bouige 
Sent: 11 April 2018 19:44
To: users@cloudstack.apache.org
Subject: RE: ssvm NFS public ip

Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev  Envoyé : mercredi 11 avril 
2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there is 
some sort of minor bug where it takes upward of 5 minutes for ssvm to program 
the internal routes, but since this is onetime operation - I just live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige  wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my 
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM 
> and mount the nfs on them...but...the agent still not going up and the 
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource 
> class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource 
> due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our 
> deployment and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not 
> the same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>

RE: ssvm NFS public ip

[Nicolas Bouige]

Hi Paul,

I used repository from shapeblue for mgmt-server and systemvm-template.
Im going to make a new fresh install (again :/) and double check the URL.

Thanks,

Best regards,
N.B


-Message d'origine-
De : Paul Angus [mailto:paul.an...@shapeblue.com] 
Envoyé : jeudi 12 avril 2018 09:12
À : users@cloudstack.apache.org
Objet : RE: ssvm NFS public ip

Hi Nicolas, this usually happens if you mix redist and noredist builds of mgmt. 
server and system vm code.

What URLs did you use for the management server repo and the system VM 
templates?



paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 


-Original Message-
From: Nicolas Bouige 
Sent: 11 April 2018 19:44
To: users@cloudstack.apache.org
Subject: RE: ssvm NFS public ip

Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev  Envoyé : mercredi 11 avril 
2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there is 
some sort of minor bug where it takes upward of 5 minutes for ssvm to program 
the internal routes, but since this is onetime operation - I just live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige  wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my 
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM 
> and mount the nfs on them...but...the agent still not going up and the 
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource 
> class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource 
> due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our 
> deployment and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not 
> the same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>

Re: PV vs HVM guest on XenServer 7.0

[Melanie Desaive]

Hi Yiping,


Am 11.04.2018 um 23:30 schrieb Yiping Zhang:

> 
> Why does CloudStack convert just a few rhel 6.x instances into HVM mode, 
> while leaving most in PV mode?
> How would I force them back to PV guests?

To my understanding CloudStacks decides about the virtualiuzation mode
of a VM depending on the value you select in "Details"-"OS Type".

Greetings,

Melanie

-- 
--

Heinlein Support GmbH
Linux: Akademie - Support - Hosting

http://www.heinlein-support.de
Tel: 030 / 40 50 51 - 0
Fax: 030 / 40 50 51 - 19

Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein  -- Sitz: Berlin



signature.asc
Description: OpenPGP digital signature

RE: ssvm NFS public ip

[Paul Angus]

Hi Nicolas, this usually happens if you mix redist and noredist builds of mgmt. 
server and system vm code.

What URLs did you use for the management server repo and the system VM 
templates?



paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Nicolas Bouige  
Sent: 11 April 2018 19:44
To: users@cloudstack.apache.org
Subject: RE: ssvm NFS public ip

Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev  Envoyé : mercredi 11 avril 
2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there is 
some sort of minor bug where it takes upward of 5 minutes for ssvm to program 
the internal routes, but since this is onetime operation - I just live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige  wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my 
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM 
> and mount the nfs on them...but...the agent still not going up and the 
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource 
> class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource 
> due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our 
> deployment and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not 
> the same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>