Hi Daan, Thanks for the updates. We are in the process of creating a branch for our company; currently, I have made an individual one. I will follow the recommended process once we are ready on that branch.
Thanks Rajiv On Fri, Aug 8, 2025 at 6:44 PM Daan Hoogland <daan.hoogl...@gmail.com> wrote: > On Thu, Aug 7, 2025 at 2:53 PM Alex Mattioli > <alex.matti...@shapeblue.com> wrote: > ... > > > But we would appreciate early comments, if any from community > developers/users, if any. How shall we proceed and get the skeleton code > reviewed with the community ? > > > > @Daan Hoogland think you can help guiding him with this? > > > > H Rajiv, > > Creating a new plugin you would look at the code on which you base and > do a `git blame` to find prior authors. Note however there has been > some churn in the community and it pays to look into which are still > active. > > When editing an existing piece of code, it is easier, you look at who > was the most recent author and ask them for a review. > > In general a mail to d...@cloudstack.apache.org and/or users@c.a.o is > useful, as you already do. So is a discussion item on the github repo. > It is usually best if you can call people out by name or function as a > generic call to action tends to get ignored. > > Having a call and demo on CCC in Milan will also draw some attention. > :wink::wink: > > > Cheers, > > Alex > > > > From: Rajiv Jain <connect.rajivjain.virtualizat...@gmail.com> > > Sent: 07 August 2025 14:43 > > To: users@cloudstack.apache.org; Alex Mattioli < > alex.matti...@shapeblue.com>; david.se...@webtasy.com; > dev-subscr...@cloudstack.apache.org > > Subject: Re: [EXTERNAL] [DISCUSS] NetApp Storage plugin to CloudStack > > > > Hi All, > > > > Today I forked the cloudstack branch and pushed initial skeleton code > for both primary and secondary storage plugin into the forked branch, by > which all the team members started writing the further implementations > against the methods exposed for driver, lifecycle and provider interfaces. > > > > I went over the link "https://cloudstack.apache.org/developers/". > > I believe we should not raise PR for the review with the community till > we are not done with full plugin implementations. > > But we would appreciate early comments, if any from community > developers/users, if any. How shall we proceed and get the skeleton code > reviewed with the community ? > > > > Thanks > > Rajiv > > > > > > > > > > On Fri, Jul 25, 2025 at 9:21 AM Rajiv Jain < > connect.rajivjain.virtualizat...@gmail.com<mailto: > connect.rajivjain.virtualizat...@gmail.com>> wrote: > > Hi Alex, David, > > > > Thank you both for your support. > > > > @David – Yes, we plan to explore ONTAP S3 storage support in future > releases. For the initial phase, we’re targeting NFS/iSCSI for primary > storage and NFS for secondary storage. > > > > @Alex – Great to hear about your past involvement with NetApp SolidFire. > I’ll review the link you shared and will reach out if I have any follow-up > questions. > > > > I had a quick query: > > Would it be feasible to introduce additional fields or controls in the > UI for the primary storage, secondary storage, and disk offering pages? > We’re considering support for the NVMe protocol in primary storage, which > may require extending the current implementation. Would the same procedure > outlined in the documentation apply to this enhancement as well? > > > > We’d also like to stay closely engaged with you and the community as we > move forward. > > Would it be possible to present our proposed ONTAP storage plugin > design—including potential UI changes and backend extensions based on the > current framework? > > > > Thanks again, > > Rajiv Jain > > > > On Thu, Jul 24, 2025 at 7:37 PM Alex Mattioli < > alex.matti...@shapeblue.com<mailto:alex.matti...@shapeblue.com>> wrote: > > Hello Rajiv, > > > > Welcome to the CloudStack community. > > I've worked on the NetApp SolidFire plugin for CloudStack and the > documentation for that project should be a good guide on how to integrate > OnTAP on CloudStack. > > Together with NetAPP I've also helped draft integration with OnTAP > should work, but that was many years ago. I do remember it though. As an > aside, I've been using NetApp for over a decade and was working with the > A-Team for a while. > > > > Now onto your questions: > > > > 1 - https://cloudstack.apache.org/contribute/ > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home > > 2- Absolutely, the CloudStack community will be more than happy to > exchange ideas with you > > 3- those should be covered on 1, but feel free to ask. > > 4- as above. > > > > Cheers, > > Alex > > > > > > > > > > > > > > > > > > -----Original Message----- > > From: Rajiv Jain <connect.rajivjain.virtualizat...@gmail.com<mailto: > connect.rajivjain.virtualizat...@gmail.com>> > > Sent: 23 July 2025 07:56 > > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org> > > Subject: [EXTERNAL] [DISCUSS] NetApp Storage plugin to CloudStack > > > > Greetings CloudStack Community, > > > > I am a member of the NetApp Storage team, currently serving as an > architect. We are exploring the opportunity to develop a storage plugin for > Apache CloudStack that supports key functionalities such as volume > creation, snapshotting, cloning, resizing, and more. > > > > We found the official CloudStack documentation to be clear and helpful, > which enabled us to successfully set up primary storage using external > storage through static configuration. > > > > We are now investigating the dynamic allocation of ONTAP storage volumes > for primary storage provisioning. In this context, we have a few queries we > would like to discuss with the community: > > > > 1. Could you guide us on the process for contributing code to the > > CloudStack project? > > 2. Would it be appropriate to present and discuss our proposed design > > for the NetApp storage plugin? > > 3. We have reviewed the storage plugin documentation outlining vendor > > implementation requirements—are there any additional best practices we > > should be aware of? > > 4. Could you share recommendations or guidelines regarding internal > > CI/CD processes that contributors typically follow? > > 5. We appreciate your support and look forward to your guidance. > > > > > > Best regards, > > Rajiv Jain > > Architect, NetApp Storage Team > > > > -- > Daan >