-
Notifications
You must be signed in to change notification settings - Fork 52
Need a VM for development #167
Comments
Hi @johnbent - Can we use docker image created as part of #89 for this. Developer can setup VM on any platform and follow steps mentioned at #89 (comment) to generate rpm's/artifacts. Also Developer can use artifacts generated from above steps to perform CORTX deployment on local VM . Provisioner accepts target repo url as |
@shailesh-vaidya whatever. The user just have to take OVA, check out the code and be able to build and run the code right away. Makes sense? |
Hey @andriytk that's what we're working towards. Thanks for the succinct definition of done. @justinzw will be testing the instructions @shailesh-vaidya posted above and if it works (especially if it works just as your succinctly describe), @justinzw will be working to get this documented with @VenkyOS . @VenkyOS , when we get this documented, here's how I want the links to work: |
@johnbent - Noted. |
Hello @VenkyOS , @justinzw - Please let me know if you face any issues in testing build instructions located at #89 (comment) to generate rpm's/artifacts. |
@VenkyOS - Hope other than timing there no issue. Can you please document steps . It does takes around 45mins to build full stack in Jenkins environment also. |
@shailesh-vaidya - Yes. Timing is an issue. I followed your instructions in the document. Shall I document and format the same in RST format? If yes, which repository should it be placed. |
@justinzw Could you please validate steps once. @VenkyOS - I feel we can put this document in https://github.com/Seagate/cortx repo. We are using GitHub Docker registry to store docker images. Hence we can make docker image public without making https://github.com/Seagate/cortx-re public. Refer - https://github.com/orgs/Seagate/packages/container/package/cortx-build |
@justinzw , @VenkyOS Please use |
@shailesh-vaidya - Sure. But, is it fine to showcase the Known Issue. |
@VenkyOS Yes. You can showcase it as known issue. CSM team is working on fixing it. |
@shailesh-vaidya - Done. |
@andriytk @johnbent We have published docker image to build entire CORTX at https://github.com/orgs/Seagate/packages/container/package/cortx-build Instructions to build CORTX packages using this Docker image is documented at - https://github.com/Seagate/cortx/blob/main/doc/Release_Build_Creation.rst |
Does it allow build and run Motr on the VM? cc @hessio |
@andriytk This docker image supports only build Motr and the other components. Running Motr through it is not possible as of now. |
Then this is not what's needed. |
I asked @hessio to look at this also. @shailesh-vaidya, after building it, how do we run it? That, as @andriytk points out, is clearly the next step and I think @hessio got stuck there as well. |
How to start a singlenode cluster on the VM (Motr+Hare) is described at https://github.com/Seagate/cortx-hare. |
Adding details from email thread here @hessio and me tested single node cluster on the VM (Motr+Hare) is described at https://github.com/Seagate/cortx-hare/blob/main/README.md . I was able to follow document within Seagate Network . However just want to note few points,
|
Can we close this issue based on this devvm we have available in the motr repo https://github.com/Seagate/cortx-motr/releases/tag/ova-centos79 |
See also Seagate/cortx-motr#1355. Here is also CentOS 8 based OVA - https://github.com/andriytk/cortx-motr/releases/tag/centos83ova. |
Ok so it is ok to close this issue as we have this requirement? Or should we wait until Seagate/cortx-motr#1355 is merged? |
For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/EOS-28332. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue. |
Closing as as we have CentOS 8 based OVA - https://github.com/andriytk/cortx-motr/releases/tag/centos83ova and - Seagate/cortx-motr#1355 |
Issue closed |
2 similar comments
Issue closed |
Issue closed |
The release VM (OVA) that we have currently is awesome for quick deployment and testing.
However we also need a release VM (OVA) that is setup for development. Such a VM should come bundled with all the build dependencies.
Anything else @andriytk ?
The text was updated successfully, but these errors were encountered: