from:"Wido den Hollander"

Re: Dynamic routing for routed mode IPv6 and IPv4 Isolated and VPC networks

2024-05-23 Thread Wido den Hollander




Op 22/05/2024 om 14:55 schreef Alex Mattioli:

Thanks for the input Wido,


That said, you could also opt that you can specify BGP peers are zone level and 
override them at network level if one prefers. Nothing specified at >the network? 
The zone-level peers are used. If you do >specify them at the network level those 
are used. Again, think about multihop.




Have you thought about the AS number pool? This pool could be assigned 
to a network. All networks can point to the same AS number pool or have 
multiple pools where you might make different choices.


On the network level this allows you to create specific BGP filters 
based on the AS number. When these are in fixed 'blocks' you can create 
better filters.



That's exactly what I had in mind, the same way we set DNS for the zone but can 
specify at network level as well. This way we keep self-service intact for when 
end-users simply want a routed network that peers with whatever the provider 
has setup upstream but also give the ability to either peer with an user 
managed VNF upstream or an operator provided router.

I hope this way we can cater for most use cases, at least with a first simple 
implementation.

Will definitely keep multihop in mind.


+ BGP password. This would solve most use-cases from the start:

- BGP peer on zone level
  - override on network level
- AS number pool
  - networks refer to this pool
- BGP multihop enabled yes or no
  - zone level
  - network level override
- BGP password

Wido



Cheers,
Alex


  



-Original Message-
From: Wido den Hollander 
Sent: Monday, May 20, 2024 8:22 PM
To: dev@cloudstack.apache.org; Alex Mattioli ; 
us...@cloudstack.apache.org; adietr...@ussignal.com
Subject: Re: Dynamic routing for routed mode IPv6 and IPv4 Isolated and VPC 
networks



Op 20/05/2024 om 14:45 schreef Alex Mattioli:

Hi Alex,

In this scenario:


I think adding the ability to add network specific peers as mentioned in one of 
>your prior replies would still allow the level of control some operators (myself 
>included) may desire.


How do you propose network specific peers to be implemented?



I do agree with Alex (Dietrich) that I think BGP peers should be configured per 
network. There is no guarantee that every VLAN/VNI
(VXLAN) ends up at the same pair of routers. Technically there is also no need 
to do so.

Let's say I have two VNI (VXLAN):

VNI 500:
Router 1: 192.168.153.1 / 2001:db8::153:1 Router 2: 192.168.153.2 / 
2001:db8::153:2

VNI 600:
Router 1: 192.168.155.1 / 2001:db8::155:1 Router 2: 192.168.155.2 / 
2001:db8::155:2

In these case you would say that the upstream BGP peers are .153.1/2,
.155.1/2 (and their IPv6 addresses). No need for BGP multihop.

Talking about multihop, I would make that optional, people might want to have 
two central BGP routers where each VR peers with (multihop) and those routers 
distribute the routes into the network again.

Per network you create you also provide the ASN range, but even better would be 
to refer to a pool. You can use one pool for your zone by referencing every 
network to the same pool are simply use multiple pools if your network requires 
so.

That said, you could also opt that you can specify BGP peers are peer level and 
override them at network level if one prefers. Nothing specified at the 
network? The zone-level peers are used. If you do specify them at the network 
level those are used. Again, think about multihop.

Wido


Regards
Alex


   



-Original Message-
From: Dietrich, Alex 
Sent: Monday, May 20, 2024 2:21 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: Dynamic routing for routed mode IPv6 and IPv4 Isolated
and VPC networks

Hi Alex,

This may be a difference in perspective in implementation of BGP at the tenant 
level. I see the ability this would provide to seamlessly establishing those 
peering relationships with minimal intervention (helping scalability).

I think adding the ability to add network specific peers as mentioned in one of 
your prior replies would still allow the level of control some operators 
(myself included) may desire.

Thanks,
Alex

[photo]<http://www.ussignal.com/>

Alex Dietrich
Senior Network Engineer, US Signal

616-233-5094  |
www.ussignal.com<https://www.ussignal.com>  |
adietr...@ussignal.com<mailto:adietr...@ussignal.com>

201 Ionia Ave SW, Grand Rapids, MI
49503<https://maps.google.com/?q=201%20Ionia%20Ave%20SW,%20Grand%20Rap
ids,%20MI%2049503>

[linkedin]<https://www.linkedin.com/company/us-signal/>

[facebook]<https://www.facebook.com/ussignalcom/>

[youtube]<https://www.youtube.com/channel/UCaFBGFfXmHziWGTFqjGzaWw>

IMPORTANT: The contents of this email are confidential. Information is intended 
for the named recipient(s) only. If you have received this email by mistake, 
please notify the sender immediately and do not disclose the contents to anyone 
or make copies thereof.

[__tpx__]
From: Alex

Re: Dynamic routing for routed mode IPv6 and IPv4 Isolated and VPC networks

2024-05-20 Thread Wido den Hollander

AS numbers 
presented to the zone)

This implementation could also be used for Shared Networks, in which case the 
destination advertised via BGP is to the gateway of the shared network.

There could also be an offering where we allow for end users to setup the BGP 
parameters for their Isolated or VPC networks, which can then peer with 
upstream VNF(s).

Any and all input is very welcome...

Taking the liberty to tag some of you: @Wei Zhou<mailto:wei.z...@shapeblue.com> @Wido den 
Hollander<mailto:w...@widodh.nl> @Kristaps Čudars<mailto:kristaps.cud...@telia.lv>

Cheers,
Alex

Re: Dynamic routing for routed mode IPv6 and IPv4 Isolated and VPC networks

2024-05-17 Thread Wido den Hollander


My apologies! I totally missed this one. Commments inline.

Op 15/05/2024 om 14:55 schreef Alex Mattioli:

Hi all,

Does anyone have an opinion on the implementation of dynamic routing in 
Isolated networks and VPCs?

So far the design is:

1 - Operator configures one or more BGP peers for a given Zone (with different 
metrics)
2 - Operator presents a pool of Private AS numbers to the Zone (just like we do 
for VLANs)
3 - When a network is created with an offering which has dynamic routing 
enabled an AS number is allocated to the network
4 - ACS configures the BGP session on the VR (using FRR), advertising all its 
connected networks



I would suggest that the upstream router (Juniper, Frr, etc) should then 
use Dynamic BGP neihbors.


On JunOS this is the "allow" statement [0]. The VR would indeed get an 
AS assigned by ACS and the network should know the 1, 2 or X upstream 
routers it can peer with. I do suggest we add BGP passwords/encryption 
from the start for safety reasons.


"allow 192.168.1.0/24"

On JunOS this allows any router within that subnet to establish a BGP 
sessions (and when the BGP password matches).


On the VR you just need to make sure you properly configure the BGP 
daemon and it points to the right upstream routers.


[0]: 
https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/allow-edit-protocols-bgp.html



Any and all input will be very welcome.

Cheers,
Alex


  


From: Alex Mattioli
Sent: Wednesday, April 17, 2024 3:25 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Dynamic routing for routed mode IPv6 and IPv4 Isolated and VPC networks

Hi all,

I'd like to brainstorm dynamic routing in ACS (yes, again... for the newcomers 
to this mailing list - this has been discussed multiple times in the past 10+ 
years)

ACS 4.17 has introduced routed mode for IPv6 in Isolated networks and VPCs, we 
are currently working on extending that to IPv4 as well, which will support the 
current NAT'ed mode and also a routed mode (inspired by the NSX integration 
https://www.youtube.com/watch?v=f7ao-vv7Ahk).

With stock ACS (i.e. without NSX or OpenSDN) this routing is purely static, with the 
operator being responsible to add static routes to the Isolated network or VPC tiers via 
the "public" (outside) IP of the virtual router.

The next step on this journey is to add some kind of dynamic routing. One way 
that I have in mind is using dynamic BGP:

1 - Operator configures one or more BGP peers for a given Zone (with different 
metrics)
2 - Operator presents a pool of Private AS numbers to the Zone (just like we do 
for VLANs)
3 - When a network is created with an offering which has dynamic routing 
enabled an AS number is allocated
4 - ACS configures the BGP session on the VR, advertising all its connected 
networks

This way there's no need to reconfigure the upstream router for each new ACS 
network (it just needs to allow dynamic BGP peering from the pool of AS numbers 
presented to the zone)

This implementation could also be used for Shared Networks, in which case the 
destination advertised via BGP is to the gateway of the shared network.

There could also be an offering where we allow for end users to setup the BGP 
parameters for their Isolated or VPC networks, which can then peer with 
upstream VNF(s).

Any and all input is very welcome...

Taking the liberty to tag some of you: @Wei Zhou<mailto:wei.z...@shapeblue.com> @Wido den 
Hollander<mailto:w...@widodh.nl> @Kristaps Čudars<mailto:kristaps.cud...@telia.lv>

Cheers,
Alex

Re: CloudStack Collaboration conference 2024 - Registration is NOW OPEN

2024-04-08 Thread Wido den Hollander


Great! I'm going to be there! :-)

Wido

Op 08/04/2024 om 16:41 schreef Ivet Petrova:

Hi All,

I am delighted to announce that the registration for CloudStack Collaboration 
Conference 2024 is now open.
I also would like to encourage you all to register here: 
https://www.eventbrite.com/e/cloudstack-collaboration-conference-2024-tickets-879401903767

This year, CCC2024 will require a ticket purchase to attend. The reason for 
this is that as you know, our event relies entirely on community support and 
sponsorship, so that we can organise it on an yearly basis. The CloudStack 
Collaboration Conference 2024 is a non-profit event, and we use all the 
sponsorship for the sake of the event - venue, catering, welcome bags for the 
attendees, etc.

IMPORTANT: The CloudStack Collaboration Conference is and will always be a free 
to attend event for all project committers. Use promo code CommitterFREE24 for 
registration.

--

The CloudStack Collaboration Conference 2024 Ticket Options are:

Super Early bird: 69 EUR - available until June 15th
Early bird: 99 EUR - available until September 15th
Standard Price - 199 EUR

The ticket fee includes:
- Hackathon Participation
- Access to all sessions and workshops
- Coffee breaks
- Lunch included for Nov 21 and Nov 22
- Drinks after the talks on Nov 21
- Welcome bag with a CloudStack T-shirt and swags


Free Passes are available for:

   *   Speakers
   *   Sponsors
   *   Committers - with promo code
   *   Sponsors will have a discount code to invite their customers and 
partners to join the event

Registrations with a promo code are a subject to review.

--

CCC2024 - Exclusive In-Person Experience in 2024
This year's conference is breaking new ground by going exclusively in-person. 
After careful consideration, collecting feedback from the community and 
planning, this year we will offer to the community the opportunity to meet 
face-to-face, fostering deeper connections and more meaningful interactions 
than ever before.
We did our best to deliver the CloudStack Community to everybody interested 
during the pandemic time for a few years. Now, we are focusing on growing the 
community and giving a chance to all contributors, committers and people 
interested into the project, to meet in-person and interact in a better way.

--

Register here: 
https://www.eventbrite.com/e/cloudstack-collaboration-conference-2024-tickets-879401903767

--

CFP is also OPEN:
The call for speakers is also open here: 
https://docs.google.com/forms/d/e/1FAIpQLSdzhEy-v68wyVQcBY3AnQT7OeDVs4xnfvlt3wIlLxV50dP11w/viewform



Best regards,

Re: CSEUG - September, Germany

2024-03-01 Thread Wido den Hollander





Op 28/02/2024 om 16:29 schreef Ivet Petrova:

Hi all,

I would like to propose to organise the CSEUG next meeting on September 12th in 
Germany.
I already had a few informal conversations with community members in Germany, 
who are willing to help.
Do you all think the date is OK and we can meet there?


Works for me on 12-09. Just wondering, Germany is big, which city are we 
looking at?


Frankfurt? Berlin? München? Düsseldorf? :-)

Wido



I consider the usual formal of half day talks and will need 5-6 speakers on 
place.

Best regards,

Re: [VOTE] next version 20 instead of 4.20

2024-02-19 Thread Wido den Hollander


+1

Op 19/02/2024 om 13:49 schreef Daan Hoogland:

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
counted please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning
scheme. The result would be that the next major version will be 20
instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
and the versions are processed numerically there are no technical
impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

Re: new website is life

2024-02-07 Thread Wido den Hollander


Nice, very nice!

Op 07/02/2024 om 09:22 schreef Daan Hoogland:

People,
we brought the new website. Please all have a look at
https://cloudstack.apache.org

thanks for any feedback

Re: [PROPOSAL] version naming : drop the 4.

2024-01-24 Thread Wido den Hollander





Op 24/01/2024 om 10:47 schreef Daan Hoogland:

personally I don't like the months too much. They tie us down to a
release schedule that we have proven not to be able to maintain. a
year as number restricts us to just one major release that year, i.e.
only one moment for new integrations or major features. S I am for the
more liberal 20.x and if we make a second one some year we can freely
add a number.



Our mails just crossed :-) Timing!

Does .MM tie you down to a specific schedule? You can release 
whenever you want, right? The version depends on when you release.


But I'm ok with just going with an number. 24, then 25, then 26, etc. 
Something else then 4.x for ever.


Wido


On Wed, Jan 24, 2024 at 12:27 AM Wei ZHOU  wrote:


Yes, the ubuntu version naming is the best in my opinion.
Other than the version naming, we need to decide the frequency of major
releases and minor releases, which version will be LTS, how long the
LTS/normal version will be supported, etc.

Maybe a vote in the dev/users/pmc mailing list?



在 2024年1月23日星期二，Nicolas Vazquez  写道：


I like this idea as well, even if its .MM or YY.MM.

Would we want to define delivery months for releases similar to Ubuntu .04
and .10?

Regards,
Nicolas Vazquez

From: Nux 
Sent: Tuesday, January 23, 2024 6:11 PM
To: dev@cloudstack.apache.org 
Cc: Wei ZHOU 
Subject: Re: [PROPOSAL] version naming : drop the 4.

An interesting proposition, I like it.
It would also relieve us from having to come up with any over-the-top
feature or change for a major version change.

On 2024-01-23 14:49, Wido den Hollander wrote:

We could look at Ubuntu, and other projects, and call it 2025.01 if we
release it in Jan 2025.

A great post on the website, mailinglists and social media could
explain the change in versioning, but that the code doesn't change that
much.

Project has matured, etc, etc.

Re: [PROPOSAL] version naming : drop the 4.

2024-01-24 Thread Wido den Hollander





Op 24/01/2024 om 00:27 schreef Wei ZHOU:

Yes, the ubuntu version naming is the best in my opinion.
Other than the version naming, we need to decide the frequency of major
releases and minor releases, which version will be LTS, how long the
LTS/normal version will be supported, etc.

Maybe a vote in the dev/users/pmc mailing list?



I think that's a good decision.

@ Daan: Do you want to start one?

I'd prefer the .MM release schedule. We just need a good (blog)post 
to explain the new versioning.


Wido




在 2024年1月23日星期二，Nicolas Vazquez  写道：


I like this idea as well, even if its .MM or YY.MM.

Would we want to define delivery months for releases similar to Ubuntu .04
and .10?

Regards,
Nicolas Vazquez

From: Nux 
Sent: Tuesday, January 23, 2024 6:11 PM
To: dev@cloudstack.apache.org 
Cc: Wei ZHOU 
Subject: Re: [PROPOSAL] version naming : drop the 4.

An interesting proposition, I like it.
It would also relieve us from having to come up with any over-the-top
feature or change for a major version change.

On 2024-01-23 14:49, Wido den Hollander wrote:

We could look at Ubuntu, and other projects, and call it 2025.01 if we
release it in Jan 2025.

A great post on the website, mailinglists and social media could
explain the change in versioning, but that the code doesn't change that
much.

Project has matured, etc, etc.

Re: [PROPOSAL] version naming : drop the 4.

2024-01-23 Thread Wido den Hollander





Op 22/01/2024 om 12:17 schreef Wei ZHOU:

+1 with 20.0

5.0 sounds like a leap with lots of significant changes. Unfortunately it
has not been discussed what needs to be done.
20.0 (or 24.0) looks better.



We could look at Ubuntu, and other projects, and call it 2025.01 if we 
release it in Jan 2025.


A great post on the website, mailinglists and social media could explain 
the change in versioning, but that the code doesn't change that much.


Project has matured, etc, etc.

Wido


Wei

On Mon, 22 Jan 2024 at 12:01, Daan Hoogland  wrote:


João,
I think we should not consider 5.0, but go to 20,0 that is more in
line with what we've actually been doing (semantic versioning from the
second digit)

On Mon, Jan 22, 2024 at 11:53 AM Nux  wrote:


LGTM!

On 2024-01-19 19:19, João Jandre Paraquetti wrote:

Hi all,

I agree that our current versioning schema doesn't make much sense, as
"minors" introduce pretty big features; even backward incompatibilities
are introduced in minor versions sometimes.

As the current plan is to have 4.20 by June, I think we should stick to
it and still have the next "minor", and make it the last minor version
of the major 4. After so much time in the same major version, we should
plan something relevant before changing it, and June 2024 is a bit of a
tight schedule for that.

I think that we should plan to move to version 5.0.0, we could set the
release date to the end of 2024 or the start (January) of 2025; by
doing that, we have plenty of time for planning and developing amazing
features for version 5, while also preparing a cleanup of our current
APIs. For instance, we are working on the following major developments:
KVM differential snapshots/backups without needing extra software;
theme management system (white label portal for ACS); native
snapshot/backup for VMware (without needing Veeam) to make it similar
to what ACS does with XenServer and KVM; Operators backup (which are
different from end-user backups); and many other items.

What do you guys think?

Best regards,
João Jandre.

On 1/19/24 10:39, Daan Hoogland wrote:

devs, PMC,

as we are closing in on 4.19 I want to propose that we drop the 4. in
our versioning scheme. We've been discussing 5 but no real initiatives
have been taken. Nowadays big features go into our "minor"
dot-releases. In my opinion this warrants promoting those version to
the status of major and dropping the 4..

technically this won't be an issue as 20 > 4 and out upgrade scheme
supports a step like that.

any thoughts?





--
Daan

Re: Apache CloudStack and Ceph Day - February 22, Amsterdam

2024-01-09 Thread Wido den Hollander





Op 09/01/2024 om 13:45 schreef Ivet Petrova:

Dear community members,

We managed to finalised the date for our joint event with the Ceph community.
I am happy to share that we are doing it on February 22nd, in Amsterdam, 
Netherlands.
The event will be hosted by Adyen, the address is: Rokin 49, 1012 KK Amsterdam, 
The Netherlands

Two things at this stage:

1. We still have a few speaking slots free (actually 2 slots only). If you are 
interested to present at the event, please submit your talk proposal now.
https://forms.gle/TnBfxS2cKWfe28CS6

2. We would be happy if we can see more people from the community, so register 
as an attendee here:
https://www.eventbrite.nl/e/cloudstack-and-ceph-day-netherlands-2024-tickets-700177167757

Look forward to meeting you in Amsterdam!


Yes! That's like my backyard. I'll be there!

Wido



Best regards,

Object Store browser connects over HTTP while HTTPS is set in URL

2023-12-20 Thread Wido den Hollander


Hi,

While testing the Ceph RGW plugin [0] for the Object Store driver I 
noticed the bucket browser isn't working.


So I debugged my Firefox browser and I noticed that it tries to connect 
to http://ceph01.holfra.eu/ (not SSL) while the store's URL is 
httpS://ceph01.holfra.eu/


My debugger says:

"Blocked loading mixed active content 
“http://ceph01.holfra.eu/wido02?location”request.js:150:9;


I looked at ObjectStoreBrowser.vue [1] and found this piece of code:

initMinioClient () {
  if (!this.client) {
const url = 
/https?:\/\/([^/]+)\/?/.exec(this.resource.url.split(this.resource.name)[0])[1]

const isHttps = /^https/.test(url)
this.client = new Minio.Client({
  endPoint: url.split(':')[0],
  port: url.split(':').length > 1 ? parseInt(url.split(':')[1]) 
: isHttps ? 443 : 80,

  useSSL: isHttps,
  accessKey: this.resource.accesskey,
  secretKey: this.resource.usersecretkey
})
this.listObjects()
  }
},


Based on if the URL starts with http or https it should select SSL or 
not, but in my case it selects HTTP while the URL contains HTTPS.


My JavaScript is a bit rusty, anybody else with ideas?

Wido

[0]: https://github.com/apache/cloudstack/pull/8389
[1]: 
https://github.com/apache/cloudstack/blob/1411da1a22bc6aa26634f3038475e3d5fbbcd6bb/ui/src/components/view/ObjectStoreBrowser.vue#L449

Re: New Object Storage - Huawei OBS

2023-12-20 Thread Wido den Hollander


It is working now!

PR is out: https://github.com/apache/cloudstack/pull/8389

On 12/16/23 13:14, Wido den Hollander wrote:



On 12/15/23 20:09, Wei ZHOU wrote:

Hi Wido,

I just tested your branch, it looks ok (
https://github.com/wido/cloudstack/commits/ceph-object-store).



Yes, it works now! I had old files in my classpath... (rookie mistake!)

I get an error about an invalid URL, but that's something else:

Error: (HTTP 530, error code ) http://ceph01..eu/ is not a valid 
URL


2023-12-16 12:13:25,737 ERROR [o.a.c.a.c.a.s.AddObjectStoragePoolCmd] 
(qtp1970436060-18:ctx-9cb56831 ctx-99f41e21) (logid:c93cae1f) Exception:
com.cloud.exception.InvalidParameterValueException: 
https://ceph01.xxx.eu/ is not a valid URL


Looking into this!

Wido



I got an error which is because I input invalid host/keys

2023-12-15 19:07:22,313 DEBUG [o.a.c.s.d.l.CephObjectStoreLifeCycleImpl]
(qtp775386112-17:ctx-9be6ad79 ctx-b4cdcdd0) (logid:3a8340e9) Error while
initializing Ceph RGW Object Store: IOException
2023-12-15 19:07:22,313 DEBUG [c.c.s.StorageManagerImpl]
(qtp775386112-17:ctx-9be6ad79 ctx-b4cdcdd0) (logid:3a8340e9) Failed to 
add

object store: Error while initializing Ceph RGW Object Store. Invalid
credentials or URL
java.lang.RuntimeException: Error while initializing Ceph RGW Object 
Store.

Invalid credentials or URL
at
org.apache.cloudstack.storage.datastore.lifecycle.CephObjectStoreLifeCycleImpl.initialize(CephObjectStoreLifeCycleImpl.java:87)
at
com.cloud.storage.StorageManagerImpl.discoverObjectStore(StorageManagerImpl.java:3777)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)


-Wei

On Fri, 15 Dec 2023 at 17:18, Wido den Hollander  wrote:




Op 15/12/2023 om 13:54 schreef Wei ZHOU:

Hi Wido,

It looks you need a file like


https://github.com/apache/cloudstack/blob/main/plugins/storage/object/simulator/src/main/resources/META-INF/cloudstack/storage-object-simulator/spring-storage-object-simulator-context.xml




Tnx. But that didn't solve it. The module seems to load according to the
mgmt server log, but I can't add the storage. Exception is the same.

Wido


-Wei

On Fri, 15 Dec 2023 at 13:40, Wido den Hollander 


wrote:




On 12/15/23 09:41, Ronald Feicht wrote:

Hi Kishan,


when I add my module to client/pom.xml I get the following error and

http://192.168.17.252:8080/client/ returns "HTTP ERROR 503 Service
Unavailable" because of the following exception:


[WARNING] Failed startup of context

o.e.j.m.p.JettyWebAppContext@1df8ea34



{/client,file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/,UNAVAILABLE}{file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/}

java.lang.NullPointerException
   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with

(DefaultModuleDefinitionSet.java:104)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:263)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:251)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts

(DefaultModuleDefinitionSet.java:96)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load

(DefaultModuleDefinitionSet.java:79)

   at



org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules

(ModuleBasedContextFactory.java:37)

   at

org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init
(CloudStackSpringContext.java:70)

   at



org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.

(CloudStackSpringContext.java:57)

   at



org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.

(CloudStackSpringContext.java:61)

   at



org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized

(CloudStackContextLoaderListener.java:52)

   at

org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized
(ContextHandle

Re: New Object Storage - Huawei OBS

2023-12-19 Thread Wido den Hollander





Op 14/12/2023 om 10:51 schreef Ronald Feicht:

Hi,

I am trying to write an Object Storage plugin for Huawei OBS using Minio as example. I 
added my plugin code to the plugins/storage/object/ directory, added my plugin into 
plugins/pom.xml and added the string 'Huawei OBS' to AddObjectStorage.vue for the 
dropdown in the UI. But when I select that dropdown entry and click "Save" in 
the UI the following exception is thrown:


Great to see! I'm working on the Ceph plugin: 
https://github.com/wido/cloudstack/commits/ceph-object-store


I will be changing something to the framework where a BucketTO is added 
and passed, not just a String containing the bucket's name.


My PR will go out next week or after Christmas I think.

Wido


com.cloud.exception.InvalidParameterValueException: can't find object store 
provider: Huawei OBS
 at 
com.cloud.storage.StorageManagerImpl.discoverObjectStore(StorageManagerImpl.java:3743)
 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
 at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
 at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
 at com.sun.proxy.$Proxy119.discoverObjectStore(Unknown Source)
 at 
org.apache.cloudstack.api.command.admin.storage.AddObjectStoragePoolCmd.execute(AddObjectStoragePoolCmd.java:117)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:172)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:782)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:603)
 at 
com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:347)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:154)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:151)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:105)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at 
org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386)
 at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617)
 at 
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:226)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604)
 at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
 at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590)
 at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
 at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
 at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300)
 at

Re: New Object Storage - Huawei OBS

2023-12-16 Thread Wido den Hollander





On 12/15/23 20:09, Wei ZHOU wrote:

Hi Wido,

I just tested your branch, it looks ok (
https://github.com/wido/cloudstack/commits/ceph-object-store).



Yes, it works now! I had old files in my classpath... (rookie mistake!)

I get an error about an invalid URL, but that's something else:

Error: (HTTP 530, error code ) http://ceph01..eu/ is not a valid URL

2023-12-16 12:13:25,737 ERROR [o.a.c.a.c.a.s.AddObjectStoragePoolCmd] 
(qtp1970436060-18:ctx-9cb56831 ctx-99f41e21) (logid:c93cae1f) Exception:
com.cloud.exception.InvalidParameterValueException: 
https://ceph01.xxx.eu/ is not a valid URL


Looking into this!

Wido



I got an error which is because I input invalid host/keys

2023-12-15 19:07:22,313 DEBUG [o.a.c.s.d.l.CephObjectStoreLifeCycleImpl]
(qtp775386112-17:ctx-9be6ad79 ctx-b4cdcdd0) (logid:3a8340e9) Error while
initializing Ceph RGW Object Store: IOException
2023-12-15 19:07:22,313 DEBUG [c.c.s.StorageManagerImpl]
(qtp775386112-17:ctx-9be6ad79 ctx-b4cdcdd0) (logid:3a8340e9) Failed to add
object store: Error while initializing Ceph RGW Object Store. Invalid
credentials or URL
java.lang.RuntimeException: Error while initializing Ceph RGW Object Store.
Invalid credentials or URL
at
org.apache.cloudstack.storage.datastore.lifecycle.CephObjectStoreLifeCycleImpl.initialize(CephObjectStoreLifeCycleImpl.java:87)
at
com.cloud.storage.StorageManagerImpl.discoverObjectStore(StorageManagerImpl.java:3777)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)


-Wei

On Fri, 15 Dec 2023 at 17:18, Wido den Hollander  wrote:




Op 15/12/2023 om 13:54 schreef Wei ZHOU:

Hi Wido,

It looks you need a file like


https://github.com/apache/cloudstack/blob/main/plugins/storage/object/simulator/src/main/resources/META-INF/cloudstack/storage-object-simulator/spring-storage-object-simulator-context.xml




Tnx. But that didn't solve it. The module seems to load according to the
mgmt server log, but I can't add the storage. Exception is the same.

Wido


-Wei

On Fri, 15 Dec 2023 at 13:40, Wido den Hollander 


On 12/15/23 09:41, Ronald Feicht wrote:

Hi Kishan,


when I add my module to client/pom.xml I get the following error and

http://192.168.17.252:8080/client/ returns "HTTP ERROR 503 Service
Unavailable" because of the following exception:


[WARNING] Failed startup of context

o.e.j.m.p.JettyWebAppContext@1df8ea34



{/client,file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/,UNAVAILABLE}{file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/}

java.lang.NullPointerException
   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with

(DefaultModuleDefinitionSet.java:104)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:263)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:268)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule

(DefaultModuleDefinitionSet.java:251)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts

(DefaultModuleDefinitionSet.java:96)

   at



org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load

(DefaultModuleDefinitionSet.java:79)

   at



org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules

(ModuleBasedContextFactory.java:37)

   at

org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init
(CloudStackSpringContext.java:70)

   at



org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.

(CloudStackSpringContext.java:57)

   at



org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.

(CloudStackSpringContext.java:61)

   at



org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized

(CloudStackContextLoaderListener.java:52)

   at

org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized
(ContextHandler.java:933)

   at

org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized
(ServletContextHandler.java:553)

   at org.eclipse.jetty.server.handler.ContextHandler.st

Re: New Object Storage - Huawei OBS

2023-12-15 Thread Wido den Hollander





Op 15/12/2023 om 13:54 schreef Wei ZHOU:

Hi Wido,

It looks you need a file like
https://github.com/apache/cloudstack/blob/main/plugins/storage/object/simulator/src/main/resources/META-INF/cloudstack/storage-object-simulator/spring-storage-object-simulator-context.xml



Tnx. But that didn't solve it. The module seems to load according to the 
mgmt server log, but I can't add the storage. Exception is the same.


Wido


-Wei

On Fri, 15 Dec 2023 at 13:40, Wido den Hollander 
wrote:




On 12/15/23 09:41, Ronald Feicht wrote:

Hi Kishan,


when I add my module to client/pom.xml I get the following error and

http://192.168.17.252:8080/client/ returns "HTTP ERROR 503 Service
Unavailable" because of the following exception:


[WARNING] Failed startup of context o.e.j.m.p.JettyWebAppContext@1df8ea34

{/client,file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/,UNAVAILABLE}{file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/}

java.lang.NullPointerException
  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with
(DefaultModuleDefinitionSet.java:104)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:263)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:268)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:268)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:268)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:268)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:268)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
(DefaultModuleDefinitionSet.java:251)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts
(DefaultModuleDefinitionSet.java:96)

  at

org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load
(DefaultModuleDefinitionSet.java:79)

  at

org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules
(ModuleBasedContextFactory.java:37)

  at

org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init
(CloudStackSpringContext.java:70)

  at

org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.
(CloudStackSpringContext.java:57)

  at

org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.
(CloudStackSpringContext.java:61)

  at

org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized
(CloudStackContextLoaderListener.java:52)

  at

org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized
(ContextHandler.java:933)

  at

org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized
(ServletContextHandler.java:553)

  at org.eclipse.jetty.server.handler.ContextHandler.startContext

(ContextHandler.java:892)

  at org.eclipse.jetty.servlet.ServletContextHandler.startContext

(ServletContextHandler.java:356)

  at org.eclipse.jetty.webapp.WebAppContext.startWebapp

(WebAppContext.java:1445)

  at org.eclipse.jetty.maven.plugin.JettyWebAppContext.startWebapp

(JettyWebAppContext.java:328)

  at org.eclipse.jetty.webapp.WebAppContext.startContext

(WebAppContext.java:1409)

  at org.eclipse.jetty.server.handler.ContextHandler.doStart

(ContextHandler.java:825)

  at org.eclipse.jetty.servlet.ServletContextHandler.doStart

(ServletContextHandler.java:275)

  at org.eclipse.jetty.webapp.WebAppContext.doStart

(WebAppContext.java:524)

  at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart

(JettyWebAppContext.java:397)

  at org.eclipse.jetty.util.component.AbstractLifeCycle.start

(AbstractLifeCycle.java:72)

  at org.eclipse.jetty.util.component.ContainerLifeCycle.start

(ContainerLifeCycle.java:169)

  at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart

(ContainerLifeCycle.java:117)

  at org.eclipse.jetty.server.handler.AbstractHandler.doStart

(AbstractHandler.java:97)

  at org.eclipse.jetty.util.component.AbstractLifeCycle.start

(AbstractLifeCycle.java:72)

  at org.eclipse.jetty.util.component.ContainerLifeCycle.start

(ContainerLifeCycle.java:169)

  at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart

(ContainerLifeCycle.java:117)

  at org.eclipse.jetty.server.handler.AbstractHandler.doStart

(AbstractHandler.java:97)

  at org.eclipse.jetty.util.component.AbstractLifeCycle.start

(AbstractLifeCycle.java:72)

  at org.eclipse.jetty.util.component.ContainerLifeC

Re: New Object Storage - Huawei OBS

2023-12-15 Thread Wido den Hollander





On 12/15/23 09:41, Ronald Feicht wrote:

Hi Kishan,


when I add my module to client/pom.xml I get the following error and 
http://192.168.17.252:8080/client/ returns "HTTP ERROR 503 Service Unavailable" 
because of the following exception:

[WARNING] Failed startup of context 
o.e.j.m.p.JettyWebAppContext@1df8ea34{/client,file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/,UNAVAILABLE}{file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/}
java.lang.NullPointerException
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with
 (DefaultModuleDefinitionSet.java:104)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:263)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:268)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:268)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:268)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:268)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:268)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
 (DefaultModuleDefinitionSet.java:251)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts
 (DefaultModuleDefinitionSet.java:96)
 at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load 
(DefaultModuleDefinitionSet.java:79)
 at 
org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules
 (ModuleBasedContextFactory.java:37)
 at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init 
(CloudStackSpringContext.java:70)
 at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext. 
(CloudStackSpringContext.java:57)
 at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext. 
(CloudStackSpringContext.java:61)
 at 
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized
 (CloudStackContextLoaderListener.java:52)
 at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized 
(ContextHandler.java:933)
 at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized 
(ServletContextHandler.java:553)
 at org.eclipse.jetty.server.handler.ContextHandler.startContext 
(ContextHandler.java:892)
 at org.eclipse.jetty.servlet.ServletContextHandler.startContext 
(ServletContextHandler.java:356)
 at org.eclipse.jetty.webapp.WebAppContext.startWebapp 
(WebAppContext.java:1445)
 at org.eclipse.jetty.maven.plugin.JettyWebAppContext.startWebapp 
(JettyWebAppContext.java:328)
 at org.eclipse.jetty.webapp.WebAppContext.startContext 
(WebAppContext.java:1409)
 at org.eclipse.jetty.server.handler.ContextHandler.doStart 
(ContextHandler.java:825)
 at org.eclipse.jetty.servlet.ServletContextHandler.doStart 
(ServletContextHandler.java:275)
 at org.eclipse.jetty.webapp.WebAppContext.doStart (WebAppContext.java:524)
 at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart 
(JettyWebAppContext.java:397)
 at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:72)
 at org.eclipse.jetty.util.component.ContainerLifeCycle.start 
(ContainerLifeCycle.java:169)
 at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart 
(ContainerLifeCycle.java:117)
 at org.eclipse.jetty.server.handler.AbstractHandler.doStart 
(AbstractHandler.java:97)
 at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:72)
 at org.eclipse.jetty.util.component.ContainerLifeCycle.start 
(ContainerLifeCycle.java:169)
 at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart 
(ContainerLifeCycle.java:117)
 at org.eclipse.jetty.server.handler.AbstractHandler.doStart 
(AbstractHandler.java:97)
 at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:72)
 at org.eclipse.jetty.util.component.ContainerLifeCycle.start 
(ContainerLifeCycle.java:169)
 at org.eclipse.jetty.server.Server.start (Server.java:407)
 at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart 
(ContainerLifeCycle.java:110)
 at org.eclipse.jetty.server.handler.AbstractHandler.doStart 
(AbstractHandler.java:97)
 at org.eclipse.jetty.server.Server.doStart (Server.java:371)
 at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:72)
 at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty 
(AbstractJettyMojo.java:450)
 at

Re: New Object Storage - Huawei OBS

2023-12-14 Thread Wido den Hollander





Op 14/12/2023 om 10:51 schreef Ronald Feicht:

Hi,

I am trying to write an Object Storage plugin for Huawei OBS using Minio as example. I 
added my plugin code to the plugins/storage/object/ directory, added my plugin into 
plugins/pom.xml and added the string 'Huawei OBS' to AddObjectStorage.vue for the 
dropdown in the UI. But when I select that dropdown entry and click "Save" in 
the UI the following exception is thrown:


Great to see! I'm working on the Ceph plugin: 
https://github.com/wido/cloudstack/commits/ceph-object-store


I will be changing something to the framework where a BucketTO is added 
and passed, not just a String containing the bucket's name.


My PR will go out next week or after Christmas I think.

Wido


com.cloud.exception.InvalidParameterValueException: can't find object store 
provider: Huawei OBS
 at 
com.cloud.storage.StorageManagerImpl.discoverObjectStore(StorageManagerImpl.java:3743)
 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
 at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
 at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
 at com.sun.proxy.$Proxy119.discoverObjectStore(Unknown Source)
 at 
org.apache.cloudstack.api.command.admin.storage.AddObjectStoragePoolCmd.execute(AddObjectStoragePoolCmd.java:117)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:172)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:782)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:603)
 at 
com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:347)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:154)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:151)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:105)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at 
org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386)
 at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617)
 at 
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:226)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604)
 at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
 at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590)
 at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
 at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
 at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300)
 at

Re: Question about ObjectStoreDriver for implementing Ceph driver

2023-12-12 Thread Wido den Hollander





Op 12/12/2023 om 04:45 schreef Rohit Yadav:

Hi Wido,

I think when the minio object storage plugin was written we didn’t have the 
limitations or foresight on how to structure the code, I would agree in 
refactoring the interface enough to allow what you’re trying to achieve.

Typically to a plugin you don’t want to pass database objects (Dao or VO) but a 
transform them as transfer object (TO) that doesn’t introduce dao or schema pkg 
dependencies to the plugin and TOs are kept as simple Java object. In the TO 
you can introduce fields and getters that suit your use cases.



Got it, thanks for the feedback! I'll work on this in two different commits.

Wido


Regards.

Regards.

From: Wido den Hollander 
Sent: Tuesday, December 12, 2023 1:28:56 AM
To: dev@cloudstack.apache.org ; kis...@apache.org 

Subject: Question about ObjectStoreDriver for implementing Ceph driver

Hi (Kishan),

I am making a first attempt [0] to implement a Ceph RGW [1] Object Store
Driver for CloudStack and I have a few questions about the code.

While implementing the Ceph RGW driver I have noticed that some methods
are provided the bucket's name (as a String) as an argument, but I'd
rather have a 'Bucket' object, for example:

public AccessControlList getBucketAcl(String bucketName, long storeId)
public boolean setBucketEncryption(String bucketName, long storeId)

In Ceph's case it would be better if these methods would get a Bucket
object, like:


public AccessControlList getBucketAcl(Bucket bucket, long storeId)

The reason is that I need to access the Account the bucket belongs to.
With Minio there is an 'Admin' client which allows you to do all these
operations as an Admin, but with Ceph there isn't. With Ceph you are
supposed to obtain the credentials (access + secret) via an Admin API
[2] and then execute these commands as the user.

Now, we have the access + secret key from the account recorded under the
account and we can access that from the Bucket object:

bucket.getAccessKey()
bucket.getSecretKey()

My proposal would be to change the signature of these methods, but
before I do so, is there any particular reason the String was passed and
not the whole Bucket object?

Thanks,

Wido

[0]: https://github.com/wido/cloudstack/commits/ceph-object-store
[1]: https://ceph.io/en/discover/technology/#object
[2]:
https://www.javadoc.io/doc/io.github.twonote/radosgw-admin4j/latest/org/twonote/rgwadmin4j/RgwAdmin.html

Question about ObjectStoreDriver for implementing Ceph driver

2023-12-11 Thread Wido den Hollander


Hi (Kishan),

I am making a first attempt [0] to implement a Ceph RGW [1] Object Store 
Driver for CloudStack and I have a few questions about the code.


While implementing the Ceph RGW driver I have noticed that some methods 
are provided the bucket's name (as a String) as an argument, but I'd 
rather have a 'Bucket' object, for example:


public AccessControlList getBucketAcl(String bucketName, long storeId)
public boolean setBucketEncryption(String bucketName, long storeId)

In Ceph's case it would be better if these methods would get a Bucket 
object, like:



public AccessControlList getBucketAcl(Bucket bucket, long storeId)

The reason is that I need to access the Account the bucket belongs to. 
With Minio there is an 'Admin' client which allows you to do all these 
operations as an Admin, but with Ceph there isn't. With Ceph you are 
supposed to obtain the credentials (access + secret) via an Admin API 
[2] and then execute these commands as the user.


Now, we have the access + secret key from the account recorded under the 
account and we can access that from the Bucket object:


bucket.getAccessKey()
bucket.getSecretKey()

My proposal would be to change the signature of these methods, but 
before I do so, is there any particular reason the String was passed and 
not the whole Bucket object?


Thanks,

Wido

[0]: https://github.com/wido/cloudstack/commits/ceph-object-store
[1]: https://ceph.io/en/discover/technology/#object
[2]: 
https://www.javadoc.io/doc/io.github.twonote/radosgw-admin4j/latest/org/twonote/rgwadmin4j/RgwAdmin.html

Re: [VOTE] Adopt Github Discusssions as Users Forum

2023-12-05 Thread Wido den Hollander


-0: Agree with Nux (see his concern in another e-mail)

Op 04/12/2023 om 22:56 schreef Nux:

-0 - I have voiced my concerns already.


On 2023-12-04 08:01, Rohit Yadav wrote:

All,

Following the discussion thread on adopting Github Discussions as 
users forum [1], I put the following proposal for a vote:



  1.  Adopt and use Github Discussions as user forums.
  2.  The Github Discussions feature is tied with the 
us...@cloudstack.apache.org mailing list (PR: 
https://github.com/apache/cloudstack/pull/8274).
  3.  Any project governance and decision-making thread such as 
voting, releases etc. should continue to use the project mailing lists.


Vote will be open for 120 hours (by Friday, 8th Dec).

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)

[1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8


Regards.

Re: [VOTE] Adopt Github Discusssions as Users Forum

2023-12-04 Thread Wido den Hollander


-0: Agree with Nux (see his concern in another e-mail)

Op 04/12/2023 om 22:56 schreef Nux:

-0 - I have voiced my concerns already.


On 2023-12-04 08:01, Rohit Yadav wrote:

All,

Following the discussion thread on adopting Github Discussions as 
users forum [1], I put the following proposal for a vote:



  1.  Adopt and use Github Discussions as user forums.
  2.  The Github Discussions feature is tied with the 
us...@cloudstack.apache.org mailing list (PR: 
https://github.com/apache/cloudstack/pull/8274).
  3.  Any project governance and decision-making thread such as 
voting, releases etc. should continue to use the project mailing lists.


Vote will be open for 120 hours (by Friday, 8th Dec).

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)

[1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8


Regards.

Re: [DISCUSS] New Design for the Apache CloudStack Website

2023-09-07 Thread Wido den Hollander





Op 31-08-2023 om 11:41 schreef Rohit Yadav:

Thanks Ivet, the new iterated design looks impressive especially some of the 
new graphical elements.

+1 to moving forward with the proposed design. Let's collect any further 
feedback and ideas from the community and if there are no objections go ahead 
with updating the preview/staging site (https://cloudstack.staged.apache.org/) 
and eventually publishing the website.

Just to be clear on the CMS integration - the ASF infra has declined supporting 
a 3rd party git-based CMS that can be used with the project website. This is 
such a shame as I had created PoCs with some rather okay-ist git-based CMS such 
as Netlify-CMS, TinaCMS and SpinalCMS which would give similar UI-based 
workflow like the old Roller-based blog did.

Nevertheless, for the purposes of publishing blogs the new Github-based 
document/markdown editor/CMS is fair enough and now allows uploading of assets 
(images, files etc.) and blog that can be edited directly for any committer 
incl. PMC members logged into Github and upon saving such changes the website 
is published by an automatic Github action that builds and published the 
websites. Unfortunately, any non-committer would need to follow the PR 
workflow. I had this documented at 
https://cloudstack.staged.apache.org/website-guide/ that I can help further 
update in this regard.



Thank you Ivet and Rohit, this is looking great! Much better then we had.

I have no real comments not objections to do. It's a great improvement 
over what we currently have.


Wido



Regards.


From: Ivet Petrova 
Sent: Wednesday, August 30, 2023 19:04
To: Giles Sirett 
Cc: dev@cloudstack.apache.org ; us...@cloudstack.apache.org 
; Marketing 
Subject: Re: [DISCUSS] New Design for the Apache CloudStack Website

Hi All,

I uploaded the design here: 
https://drive.google.com/file/d/1pef7xWWMPYAA5UkbS_XMUxrz53KB7J5t/view?usp=sharing


Kind regards,





  


On 30 Aug 2023, at 16:31, Giles Sirett 
mailto:giles.sir...@shapeblue.com>> wrote:

Hi Ivet – thanks for pushing forward with this – excited to review a new design.

On that note, I cant see a link in your mail ☹

Kind Regards
Giles


Giles Sirett
CEO
giles.sir...@shapeblue.com
www.shapeblue.com




From: Ivet Petrova 
mailto:ivet.petr...@shapeblue.com>>
Sent: Wednesday, August 30, 2023 10:14 AM
To: us...@cloudstack.apache.org; Marketing 
mailto:market...@shapeblue.com>>
Cc: dev mailto:dev@cloudstack.apache.org>>
Subject: [DISCUSS] New Design for the Apache CloudStack Website

Hello,

I would like to start a discussion on the design of the Apache CloudStack 
Website and to propose a new design for it.

As we all know, the website has not been changed for years in terms of design 
and information. The biggest issue we know we have is that the website is not 
showing the full potential of CloudStack. In addition to it during discussions 
with many community members, I have noted the following issues:
- the existing website design is old-school
- the current homepage does not collect enough information to show CloudStack's 
strengths
- current website design is missing images from the ACS UI and cannot create a 
feel for the product in the users
- the website has issues on a mobile device
- we lack any graphic and diagrams
- some important information like how to download is not very visible

I collected a lot of feedback during last months and want to propose a new up 
to date design for the website, which is attached below. The new design will 
bring:
- improved UX
- look and feel corresponding to the CloudStack's capabilities and strengths
- more graphical elements, diagrams
- better branding
- more important information, easily accessible for the potential users

I hope you will like the new design – all feedback welcome. Once we have the 
design finalised, we will use Rohit’s proposal previously of a CMS, which is 
easy to edit.

[cid:B5517475-02DA-472A-BD1D-F3B600AD28ED]

Kind regards,

Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP and Registration Now Open!

2023-07-28 Thread Wido den Hollander

Hi,

Op 24-07-2023 om 08:53 schreef Ivet Petrova:

Hi All,

- As Gregoire has mentioned, the hotel recently rebranded - maybe the new site
was launched 2-3 weeks ago. So the name of the hotel now is
https://www.ihg.com/voco/hotels/us/en/clichy/parpc/hoteldetail
It is renovated and rebranded, but location is the same.

I see! The link now seems to be fine.

However, on CloudStackcollab.org the link is partially broken.

"CCC 2023 will be taking place in the Holiday Inn/VOCO Paris, Porte de
Clichy. "

This link points to:
"https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetailhttps://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail;

Double the URL concatted.

- I have sent an email last week to the hotel to ask for some pricing/special
offer for our conference members. Will keep you posted as soon as I have
details.

- Good remark for the project website. I thought we posted there, will add the
info today.

I see it now! Shouldn't this link to https://www.cloudstackcollab.org/ ?

Because right now it goes to Hubilo directly and there isn't much
information there.

- We will add the train info also to the website official info for travelling
we plan to post. Megali from DIMSI’s team is helping us on these details.

Great! And indeed, from London you can very easily reach Paris via
Eurostar. I just booked my Thalys train tickets :-)

Wido

Kind regards,

On 23 Jul 2023, at 20:27, Gregoire LAMODIERE
mailto:g.lamodi...@dimsi.fr>> wrote:

Hi Wido,

Thanks for your message.
You are right, UK / EU people should consider coming to Paris by train.
The hotel is well connected to subways lines 13 and 14, and we (DIMSI) can help
anyone to find best way to come.

About the hotel, you are right, it's been rebranded last month, and I guess
they forgot to make a redirection from old website (HolidayInn) to new one
(vocco).
I stayed there once since the change, and result is good, with a nice rhum bar for
"change the world" late conversations.

As local player, we (still DIMSI team) will be happy to arrange a beer / diner
session.
Maybe we can discuss this @Ivet Petrova and @Jamie Pell ?

Btw, very happy to welcome the community in France next november !

Gregoire LAMODIERE
Co-fondateur & Solution architect
-----Message d'origine-
De : Wido den Hollander mailto:w...@widodh.nl>>
Envoyé : vendredi 21 juillet 2023 20:18
À : us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>; Jamie Pell
mailto:jamie.p...@shapeblue.com>>;
market...@cloudstack.apache.org<mailto:market...@cloudstack.apache.org>;
dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Objet : Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP
and Registration Now Open!

Hi Ivet,

Thanks for organizing this! I was just sharing this internally with our
colleagues throughout Europe and I noticed that the link to the hotel is
broken. The correct URL is:
https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail

A few things in addition:

- Is there a deal with the hotel for a fixed price for rooms?
- I don't see this event mentioned at the CloudStack main website
- Do we have anybody local who can help with finding bars for drinks?

I'd also like to make a recommendation to everybody from Europe to consider
coming by train instead of flying. Paris is very well connected from Brussels
(BE), Aachen (DE), Cologne (DE) and Amsterdam (NL) and ofcourse other cities in
Paris.

'Gare du Nord' and 'Gare de Lyon' are two major train stations where high speed
trains terminate.

Check out Google Maps or Thalys/TGV to see if coming by train makes sense. I'll
be doing that for sure and will make sure all my other colleagues come by train
as well.

https://en.wikipedia.org/wiki/High-speed_rail_in_Europe

See you in Paris in November!

Wido

Op 31/05/2023 om 10:48 schreef Jamie Pell:
Hi everyone,

I am pleased to share that the CloudStack Collaboration Conference 2023
registration and call for presentations is now open! Once again, this year’s
event will be a hybrid one, allowing community members who are not able to
attend in-person, to join virtually.

Submit a
Talk<https://docs.google.com/forms/d/e/1FAIpQLSdaFH8I_fubiImp6mOXpAPL8
2UfjpCgisu3WAQBMtY-geqWyA/viewform>

This year’s event will be taking place in the Holiday Inn
Paris<https://www.ihg.com/holidayinn/hotels/us/en/clichy/parpc/hoteldetail> on
November 23-24th.

If your company is interested in supporting the event by becoming a
sponsor, you can read the sponsorship
prospectus.<https://www.cloudstackcollab.org/wp-content/uploads/2023/0
2/Sponsorship-Prospectus-CCC-2023.pdf>

For further information regarding the event, visit the official event
website.<https://www.cloudstackcollab.org/>

Kind regards,

Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP and Registration Now Open!

2023-07-26 Thread Wido den Hollander

Op 26/07/2023 om 09:40 schreef Ivet Petrova:

Hi Wido,

The link on the site is fixed.
As for the project website - it links on purpose to the Hubilo platform, so
that people can see a direct registration page and make it easier for them to
register.
As you mentioned there is not enough info there - can you let me know what
would you like to see there to make the experience better?

Yesterday it was redirecting me to
https://events.hubilo.com/cloudstack-collaboration-conference-2023/login

That URL doesn't contain much, but right now the main ACS website links
to
https://events.hubilo.com/cloudstack-collaboration-conference-2023/register
and that does contain the information needed.

All good!

Wido

Kind regards,

On 25 Jul 2023, at 12:01, Wido den Hollander
mailto:w...@widodh.nl>> wrote:

Hi,

Op 24-07-2023 om 08:53 schreef Ivet Petrova:
Hi All,
- As Gregoire has mentioned, the hotel recently rebranded - maybe the new site
was launched 2-3 weeks ago. So the name of the hotel now is
https://www.ihg.com/voco/hotels/us/en/clichy/parpc/hoteldetail
It is renovated and rebranded, but location is the same.

I see! The link now seems to be fine.

However, on CloudStackcollab.org<http://CloudStackcollab.org> the link is
partially broken.

"CCC 2023 will be taking place in the Holiday Inn/VOCO Paris, Porte de Clichy."

This link points to:
"https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetailhttps://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail;

Double the URL concatted.

- I have sent an email last week to the hotel to ask for some pricing/special
offer for our conference members. Will keep you posted as soon as I have
details.
- Good remark for the project website. I thought we posted there, will add the
info today.

I see it now! Shouldn't this link to https://www.cloudstackcollab.org/ ?

Because right now it goes to Hubilo directly and there isn't much information
there.

- We will add the train info also to the website official info for travelling
we plan to post. Megali from DIMSI’s team is helping us on these details.

Great! And indeed, from London you can very easily reach Paris via Eurostar. I
just booked my Thalys train tickets :-)

Wido

Kind regards,
On 23 Jul 2023, at 20:27, Gregoire LAMODIERE
mailto:g.lamodi...@dimsi.fr><mailto:g.lamodi...@dimsi.fr>>
wrote:
Hi Wido,
Thanks for your message.
You are right, UK / EU people should consider coming to Paris by train.
The hotel is well connected to subways lines 13 and 14, and we (DIMSI) can help
anyone to find best way to come.
About the hotel, you are right, it's been rebranded last month, and I guess
they forgot to make a redirection from old website (HolidayInn) to new one
(vocco).
I stayed there once since the change, and result is good, with a nice rhum bar for
"change the world" late conversations.
As local player, we (still DIMSI team) will be happy to arrange a beer / diner
session.
Maybe we can discuss this @Ivet Petrova and @Jamie Pell ?
Btw, very happy to welcome the community in France next november !
Gregoire LAMODIERE
Co-fondateur & Solution architect
-Message d'origine-
De : Wido den Hollander
mailto:w...@widodh.nl><mailto:w...@widodh.nl>>
Envoyé : vendredi 21 juillet 2023 20:18
À : us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org><mailto:us...@cloudstack.apache.org>; Jamie Pell
mailto:jamie.p...@shapeblue.com><mailto:jamie.p...@shapeblue.com>>;
market...@cloudstack.apache.org<mailto:market...@cloudstack.apache.org><mailto:market...@cloudstack.apache.org>;
dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org>
Objet : Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP
and Registration Now Open!
Hi Ivet,
Thanks for organizing this! I was just sharing this internally with our
colleagues throughout Europe and I noticed that the link to the hotel is
broken. The correct URL is:
https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail
A few things in addition:
- Is there a deal with the hotel for a fixed price for rooms?
- I don't see this event mentioned at the CloudStack main website
- Do we have anybody local who can help with finding bars for drinks?
I'd also like to make a recommendation to everybody from Europe to consider
coming by train instead of flying. Paris is very well connected from Brussels
(BE), Aachen (DE), Cologne (DE) and Amsterdam (NL) and ofcourse other cities in
Paris.
'Gare du Nord' and 'Gare de Lyon' are two major train stations where high speed
trains terminate.
Check out Google Maps or Thalys/TGV to see if coming by train makes sense. I'll
be doing that for sure and will make sure all my other colleagues come by train
as well.
https://en.wikipedia.org/wiki/High-speed_rail_in_Europe
See you in Paris in November!
Wido
Op 31/05/2023 om 10:48 schre

Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP and Registration Now Open!

2023-07-25 Thread Wido den Hollander

Hi,

Op 24-07-2023 om 08:53 schreef Ivet Petrova:

Hi All,

I see! The link now seems to be fine.

However, on CloudStackcollab.org the link is partially broken.

"CCC 2023 will be taking place in the Holiday Inn/VOCO Paris, Porte de
Clichy. "

This link points to:
"https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetailhttps://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail;

Double the URL concatted.

- I have sent an email last week to the hotel to ask for some pricing/special
offer for our conference members. Will keep you posted as soon as I have
details.

- Good remark for the project website. I thought we posted there, will add the
info today.

I see it now! Shouldn't this link to https://www.cloudstackcollab.org/ ?

Because right now it goes to Hubilo directly and there isn't much
information there.

- We will add the train info also to the website official info for travelling
we plan to post. Megali from DIMSI’s team is helping us on these details.

Great! And indeed, from London you can very easily reach Paris via
Eurostar. I just booked my Thalys train tickets :-)

Wido

Kind regards,

On 23 Jul 2023, at 20:27, Gregoire LAMODIERE
mailto:g.lamodi...@dimsi.fr>> wrote:

Hi Wido,

As local player, we (still DIMSI team) will be happy to arrange a beer / diner
session.
Maybe we can discuss this @Ivet Petrova and @Jamie Pell ?

Btw, very happy to welcome the community in France next november !

Hi Ivet,

A few things in addition:

- Is there a deal with the hotel for a fixed price for rooms?
- I don't see this event mentioned at the CloudStack main website
- Do we have anybody local who can help with finding bars for drinks?

'Gare du Nord' and 'Gare de Lyon' are two major train stations where high speed
trains terminate.

Check out Google Maps or Thalys/TGV to see if coming by train makes sense. I'll
be doing that for sure and will make sure all my other colleagues come by train
as well.

https://en.wikipedia.org/wiki/High-speed_rail_in_Europe

See you in Paris in November!

Wido

Op 31/05/2023 om 10:48 schreef Jamie Pell:
Hi everyone,

Submit a
Talk<https://docs.google.com/forms/d/e/1FAIpQLSdaFH8I_fubiImp6mOXpAPL8
2UfjpCgisu3WAQBMtY-geqWyA/viewform>

This year’s event will be taking place in the Holiday Inn
Paris<https://www.ihg.com/holidayinn/hotels/us/en/clichy/parpc/hoteldetail> on
November 23-24th.

For further information regarding the event, visit the official event
website.<https://www.cloudstackcollab.org/>

Kind regards,

Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP and Registration Now Open!

2023-07-24 Thread Wido den Hollander


Hi Ivet,

Thanks for organizing this! I was just sharing this internally with our 
colleagues throughout Europe and I noticed that the link to the hotel is 
broken. The correct URL is: 
https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail


A few things in addition:

- Is there a deal with the hotel for a fixed price for rooms?
- I don't see this event mentioned at the CloudStack main website
- Do we have anybody local who can help with finding bars for drinks?

I'd also like to make a recommendation to everybody from Europe to 
consider coming by train instead of flying. Paris is very well connected 
from Brussels (BE), Aachen (DE), Cologne (DE) and Amsterdam (NL) and 
ofcourse other cities in Paris.


'Gare du Nord' and 'Gare de Lyon' are two major train stations where 
high speed trains terminate.


Check out Google Maps or Thalys/TGV to see if coming by train makes 
sense. I'll be doing that for sure and will make sure all my other 
colleagues come by train as well.


https://en.wikipedia.org/wiki/High-speed_rail_in_Europe

See you in Paris in November!

Wido

Op 31/05/2023 om 10:48 schreef Jamie Pell:

Hi everyone,

I am pleased to share that the CloudStack Collaboration Conference 2023 
registration and call for presentations is now open! Once again, this year’s 
event will be a hybrid one, allowing community members who are not able to 
attend in-person, to join virtually.

Register for 
CCC

Submit a 
Talk

This year’s event will be taking place in the Holiday Inn 
Paris on 
November 23-24th.

If your company is interested in supporting the event by becoming a sponsor, you can 
read the sponsorship 
prospectus.

For further information regarding the event, visit the official event 
website.

Kind regards,

Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP and Registration Now Open!

2023-07-21 Thread Wido den Hollander


Hi Ivet,

Thanks for organizing this! I was just sharing this internally with our 
colleagues throughout Europe and I noticed that the link to the hotel is 
broken. The correct URL is: 
https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail


A few things in addition:

- Is there a deal with the hotel for a fixed price for rooms?
- I don't see this event mentioned at the CloudStack main website
- Do we have anybody local who can help with finding bars for drinks?

I'd also like to make a recommendation to everybody from Europe to 
consider coming by train instead of flying. Paris is very well connected 
from Brussels (BE), Aachen (DE), Cologne (DE) and Amsterdam (NL) and 
ofcourse other cities in Paris.


'Gare du Nord' and 'Gare de Lyon' are two major train stations where 
high speed trains terminate.


Check out Google Maps or Thalys/TGV to see if coming by train makes 
sense. I'll be doing that for sure and will make sure all my other 
colleagues come by train as well.


https://en.wikipedia.org/wiki/High-speed_rail_in_Europe

See you in Paris in November!

Wido

Op 31/05/2023 om 10:48 schreef Jamie Pell:

Hi everyone,

I am pleased to share that the CloudStack Collaboration Conference 2023 
registration and call for presentations is now open! Once again, this year’s 
event will be a hybrid one, allowing community members who are not able to 
attend in-person, to join virtually.

Register for 
CCC

Submit a 
Talk

This year’s event will be taking place in the Holiday Inn 
Paris on 
November 23-24th.

If your company is interested in supporting the event by becoming a sponsor, you can 
read the sponsorship 
prospectus.

For further information regarding the event, visit the official event 
website.

Kind regards,

Re: Missing ubuntu 4.18 packages

2023-03-19 Thread Wido den Hollander


Hi,

We are aware. Those need to be build and uploaded.

Wido

Op 18-03-2023 om 13:39 schreef Curious Pandora:

Hello,

it looks like the 4.18 packages for focal/jammy/bionic are missing at
download.cloudstack.org.

Regards,

Re: Register for the CCC - Physical Attendance

2022-10-27 Thread Wido den Hollander

Looking forward to it! We'll join with 4 people from our company 
(Netherlands).


Great to see the community again. Learn from and help each other and 
afterwards enjoy a few beers.


See you all in Bulgaria!

Wido

On 10/26/22 12:59, Ivet Petrova wrote:

Hi all,
I would like to kindly ask all of you, who plan to attend the CloudStack 
Collaboration Conference physically in Sofia to register as soon as possible. I 
am finalizing the lunch and catering details and need some close to exact 
numbers for this by end of week.
Please, take a moment to complete your registration here: 
https://events.hubilo.com/cloudstack-collaboration-conference-2022/register

Thanks for the effort!
Ivet

Sent from my iPhone

Re: Running the UI on Docker container

2022-09-07 Thread Wido den Hollander





Op 07-09-2022 om 09:34 schreef Nux:

Wido,

I've just run the UI standalone on a separate machine the other day, but 
not on docker.
What I did was to install cloudstack-ui rpm package, then serve it like 
a normal site, but proxy /client to mgmt-server:8000 like described here:


https://github.com/apache/cloudstack/tree/main/ui#production



Yes, true. Our scenario is that we want to have a single VM running 
multiple versions of the UI with different config.json files.


Now technically we could also have the Proxy (NGINX/Apache) inject a 
different config.json based on the hostname/url being requested and thus 
influence the UI and how it behaves.


Running different Docker containers with different configurations is 
also possible and we aren't sure yet on which route to take.


Our main idea is that we want to personalize and customize the UI to 
better fit the look and feel of the company and other portals.


Wido


hth

---
Nux
www.nux.ro

On 2022-09-06 15:56, Wido den Hollander wrote:

Hi,

Anybody there running the UI outside the Management Server in a Docker
container like described here?

https://github.com/apache/cloudstack/tree/main/ui

I have a use-case for this we would like to investigate, but the build
currently fails [0].

Is this still relevant and supported?

Wido

[0]: https://github.com/apache/cloudstack/issues/6709

Running the UI on Docker container

2022-09-06 Thread Wido den Hollander


Hi,

Anybody there running the UI outside the Management Server in a Docker 
container like described here?


https://github.com/apache/cloudstack/tree/main/ui

I have a use-case for this we would like to investigate, but the build 
currently fails [0].


Is this still relevant and supported?

Wido

[0]: https://github.com/apache/cloudstack/issues/6709

Introducing Bart and Ruben

2022-08-08 Thread Wido den Hollander


Hi devs,

Recently Bart and Ruben (CC) joined CLDIN (was PCextreme) as DevOps 
engineers and will be working on CloudStack and start to contribute to 
the project.


In the coming months they'll finding their way around in the community 
and code and you should start seeing Pull Requests from them coming in.


We'll try to make the CCC in Bulgaria later this year!

Wido

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 958 matches

Mail list logo