Re: [Project Clearwater] Release note for Sprint Zamîn
I raised an issue on github to keep track of this: https://github.com/Metaswitch/project-clearwater-issues/issues/31 Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: 22 May 2018 09:41 To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Frank, Apologies for the slow turnaround on this question. > What is the actual intended disk configuration for the AIO image based on > vSphere? Which virtual storage controller is the target and how many vdisks > should the resulting VM have, as currently the OVA through vCenter as well as > through ESXi deploys with a single disk. It should be a single disk on the IDE 0 controller. You can see how the device creation is done in virtualbox in here: https://github.com/Metaswitch/clearwater-vm-images/blob/master/ubuntu-ovf/make_ovf.sh Cheers, Will From: William Yates Sent: 24 April 2018 10:40 To: clearwater@lists.projectclearwater.org Subject: RE: [Project Clearwater] Release note for Sprint Zamîn Thanks Frank, we'll get back on the SATA0 issue. Roger, would you be happy to raise a github issue for this, and we'll consider fixing it in a future stable release ? Also, the manual install offers another workaround, described here: https://clearwater.readthedocs.io/en/stable/All_in_one_Images.html#manual-build Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Frank Escaros-Buechsel Sent: 24 April 2018 00:09 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, After reading the documentation I do not think that a vCenter deploy is extensively tested as only ESXi deploy is mentioned in the clearwater wiki. I get exactly the same error message as you do when I try to deploy through vCenter, yet I am able to successfully deploy the OVA directly to ESXi. @Clearwater team: I modified the OVF file after extraction and removed the offending fields from Roger’s screenshot which also allows me then to deploy successfully through vCenter. I have copied the new contents of the OVF file to https://pastebin.com/raw/NStkhajn for your review. When trying to boot the VM it is complaining about not being able to connect to SATA0 controller. What is the actual intended disk configuration for the AIO image based on vSphere? Which virtual storage controller is the target and how many vdisks should the resulting VM have, as currently the OVA through vCenter as well as through ESXi deploys with a single disk. Ellis and Bono do seem to come up successfully despite the error I am seeing, which makes me think it’s purely cosmetic but with knowing the correct disk controller type for vSphere which is intended by you I can make further modifications to the OVF to avoid the cosmetic error as well: [cw-aio]ubuntu@cw-aio:~$ netstat -ano | grep 5060 tcp0 0 10.27.32.111:5060 0.0.0.0:* LISTEN off (0.00/0/0) udp0 0 10.27.32.111:5060 0.0.0.0:* off (0.00/0/0) Kind Regards, Frank Escaros-Buechsel Consulting Architect NFV fescarosbue...@vmware.com<mailto:fescarosbue...@vmware.com> Parnell House, Barrack Square, Ballincollig, Co. Cork, P31 PF68, IRL Twitter: @fbuechsel Advanced notice of absence: [VMwareLogo] From: Frank Escaros-Buechsel Sent: Friday 20 April 2018 22:03 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, Looks like a malformed ofv file for the vsphere build you are using, I can try to reproduce in my lab over the weekend. Frank Escaros-Buechsel Consulting Architect NFV Parnell House, Barrack Square, Ballincollig, Co. Cork P31 PF68, IRL Twitter: @fbuechsel On 20 Apr 2018, at 22:58, Roger Case mailto:c...@gci.com>> wrote: Hi Frank, 1. Where would I get the checksum to compare with the one I derived from the downloaded file? 2. Unzip OK. 3. Checksums of .ovf and .vmdk match those in the .mf file 4. Same error when selecting all three unzipped files to deploy ovf. 5. Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy t
Re: [Project Clearwater] Release note for Sprint Zamîn
Frank, Apologies for the slow turnaround on this question. > What is the actual intended disk configuration for the AIO image based on > vSphere? Which virtual storage controller is the target and how many vdisks > should the resulting VM have, as currently the OVA through vCenter as well as > through ESXi deploys with a single disk. It should be a single disk on the IDE 0 controller. You can see how the device creation is done in virtualbox in here: https://github.com/Metaswitch/clearwater-vm-images/blob/master/ubuntu-ovf/make_ovf.sh Cheers, Will From: William Yates Sent: 24 April 2018 10:40 To: clearwater@lists.projectclearwater.org Subject: RE: [Project Clearwater] Release note for Sprint Zamîn Thanks Frank, we'll get back on the SATA0 issue. Roger, would you be happy to raise a github issue for this, and we'll consider fixing it in a future stable release ? Also, the manual install offers another workaround, described here: https://clearwater.readthedocs.io/en/stable/All_in_one_Images.html#manual-build Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Frank Escaros-Buechsel Sent: 24 April 2018 00:09 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, After reading the documentation I do not think that a vCenter deploy is extensively tested as only ESXi deploy is mentioned in the clearwater wiki. I get exactly the same error message as you do when I try to deploy through vCenter, yet I am able to successfully deploy the OVA directly to ESXi. @Clearwater team: I modified the OVF file after extraction and removed the offending fields from Roger’s screenshot which also allows me then to deploy successfully through vCenter. I have copied the new contents of the OVF file to https://pastebin.com/raw/NStkhajn for your review. When trying to boot the VM it is complaining about not being able to connect to SATA0 controller. What is the actual intended disk configuration for the AIO image based on vSphere? Which virtual storage controller is the target and how many vdisks should the resulting VM have, as currently the OVA through vCenter as well as through ESXi deploys with a single disk. Ellis and Bono do seem to come up successfully despite the error I am seeing, which makes me think it’s purely cosmetic but with knowing the correct disk controller type for vSphere which is intended by you I can make further modifications to the OVF to avoid the cosmetic error as well: [cw-aio]ubuntu@cw-aio:~$ netstat -ano | grep 5060 tcp0 0 10.27.32.111:5060 0.0.0.0:* LISTEN off (0.00/0/0) udp0 0 10.27.32.111:5060 0.0.0.0:* off (0.00/0/0) Kind Regards, Frank Escaros-Buechsel Consulting Architect NFV fescarosbue...@vmware.com<mailto:fescarosbue...@vmware.com> Parnell House, Barrack Square, Ballincollig, Co. Cork, P31 PF68, IRL Twitter: @fbuechsel Advanced notice of absence: [VMwareLogo] From: Frank Escaros-Buechsel Sent: Friday 20 April 2018 22:03 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, Looks like a malformed ofv file for the vsphere build you are using, I can try to reproduce in my lab over the weekend. Frank Escaros-Buechsel Consulting Architect NFV Parnell House, Barrack Square, Ballincollig, Co. Cork P31 PF68, IRL Twitter: @fbuechsel On 20 Apr 2018, at 22:58, Roger Case mailto:c...@gci.com>> wrote: Hi Frank, 1. Where would I get the checksum to compare with the one I derived from the downloaded file? 2. Unzip OK. 3. Checksums of .ovf and .vmdk match those in the .mf file 4. Same error when selecting all three unzipped files to deploy ovf. 5. Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:2
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Frank, Thank you very much for testing this. Come to think of it I probably was not using vCenter Server when I initially brought up the All-In-One. It never occurred to me that that the base processes would be any different using vCenter, and I have deployed many other OVFs since deploying the server. Very interesting indeed. Really appreciate your effort! Best regards, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Monday, April 23, 2018 3:09 PM To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: RE: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, After reading the documentation I do not think that a vCenter deploy is extensively tested as only ESXi deploy is mentioned in the clearwater wiki. I get exactly the same error message as you do when I try to deploy through vCenter, yet I am able to successfully deploy the OVA directly to ESXi. @Clearwater team: I modified the OVF file after extraction and removed the offending fields from Roger’s screenshot which also allows me then to deploy successfully through vCenter. I have copied the new contents of the OVF file to https://pastebin.com/raw/NStkhajn for your review. When trying to boot the VM it is complaining about not being able to connect to SATA0 controller. What is the actual intended disk configuration for the AIO image based on vSphere? Which virtual storage controller is the target and how many vdisks should the resulting VM have, as currently the OVA through vCenter as well as through ESXi deploys with a single disk. Ellis and Bono do seem to come up successfully despite the error I am seeing, which makes me think it’s purely cosmetic but with knowing the correct disk controller type for vSphere which is intended by you I can make further modifications to the OVF to avoid the cosmetic error as well: [cw-aio]ubuntu@cw-aio:~$ netstat -ano | grep 5060 tcp0 0 10.27.32.111:5060 0.0.0.0:* LISTEN off (0.00/0/0) udp0 0 10.27.32.111:5060 0.0.0.0:* off (0.00/0/0) Kind Regards, Frank Escaros-Buechsel Consulting Architect NFV fescarosbue...@vmware.com<mailto:fescarosbue...@vmware.com> Parnell House, Barrack Square, Ballincollig, Co. Cork, P31 PF68, IRL Twitter: @fbuechsel Advanced notice of absence: [VMwareLogo] From: Frank Escaros-Buechsel Sent: Friday 20 April 2018 22:03 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, Looks like a malformed ofv file for the vsphere build you are using, I can try to reproduce in my lab over the weekend. Frank Escaros-Buechsel Consulting Architect NFV Parnell House, Barrack Square, Ballincollig, Co. Cork P31 PF68, IRL Twitter: @fbuechsel On 20 Apr 2018, at 22:58, Roger Case mailto:c...@gci.com>> wrote: Hi Frank, 1. Where would I get the checksum to compare with the one I derived from the downloaded file? 2. Unzip OK. 3. Checksums of .ovf and .vmdk match those in the .mf file 4. Same error when selecting all three unzipped files to deploy ovf. 5. Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:24 GMT+3, Roger Case mailto:c...@gci.com>> wrote: Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Ser
Re: [Project Clearwater] Release note for Sprint Zamîn
Thanks Frank, we'll get back on the SATA0 issue. Roger, would you be happy to raise a github issue for this, and we'll consider fixing it in a future stable release ? Also, the manual install offers another workaround, described here: https://clearwater.readthedocs.io/en/stable/All_in_one_Images.html#manual-build Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Frank Escaros-Buechsel Sent: 24 April 2018 00:09 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, After reading the documentation I do not think that a vCenter deploy is extensively tested as only ESXi deploy is mentioned in the clearwater wiki. I get exactly the same error message as you do when I try to deploy through vCenter, yet I am able to successfully deploy the OVA directly to ESXi. @Clearwater team: I modified the OVF file after extraction and removed the offending fields from Roger’s screenshot which also allows me then to deploy successfully through vCenter. I have copied the new contents of the OVF file to https://pastebin.com/raw/NStkhajn for your review. When trying to boot the VM it is complaining about not being able to connect to SATA0 controller. What is the actual intended disk configuration for the AIO image based on vSphere? Which virtual storage controller is the target and how many vdisks should the resulting VM have, as currently the OVA through vCenter as well as through ESXi deploys with a single disk. Ellis and Bono do seem to come up successfully despite the error I am seeing, which makes me think it’s purely cosmetic but with knowing the correct disk controller type for vSphere which is intended by you I can make further modifications to the OVF to avoid the cosmetic error as well: [cw-aio]ubuntu@cw-aio:~$ netstat -ano | grep 5060 tcp0 0 10.27.32.111:5060 0.0.0.0:* LISTEN off (0.00/0/0) udp0 0 10.27.32.111:5060 0.0.0.0:* off (0.00/0/0) Kind Regards, Frank Escaros-Buechsel Consulting Architect NFV fescarosbue...@vmware.com<mailto:fescarosbue...@vmware.com> Parnell House, Barrack Square, Ballincollig, Co. Cork, P31 PF68, IRL Twitter: @fbuechsel Advanced notice of absence: [VMwareLogo] From: Frank Escaros-Buechsel Sent: Friday 20 April 2018 22:03 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, Looks like a malformed ofv file for the vsphere build you are using, I can try to reproduce in my lab over the weekend. Frank Escaros-Buechsel Consulting Architect NFV Parnell House, Barrack Square, Ballincollig, Co. Cork P31 PF68, IRL Twitter: @fbuechsel On 20 Apr 2018, at 22:58, Roger Case mailto:c...@gci.com>> wrote: Hi Frank, 1. Where would I get the checksum to compare with the one I derived from the downloaded file? 2. Unzip OK. 3. Checksums of .ovf and .vmdk match those in the .mf file 4. Same error when selecting all three unzipped files to deploy ovf. 5. Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:24 GMT+3, Roger Case mailto:c...@gci.com>> wrote: Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Rog
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Roger, After reading the documentation I do not think that a vCenter deploy is extensively tested as only ESXi deploy is mentioned in the clearwater wiki. I get exactly the same error message as you do when I try to deploy through vCenter, yet I am able to successfully deploy the OVA directly to ESXi. @Clearwater team: I modified the OVF file after extraction and removed the offending fields from Roger’s screenshot which also allows me then to deploy successfully through vCenter. I have copied the new contents of the OVF file to https://pastebin.com/raw/NStkhajn for your review. When trying to boot the VM it is complaining about not being able to connect to SATA0 controller. What is the actual intended disk configuration for the AIO image based on vSphere? Which virtual storage controller is the target and how many vdisks should the resulting VM have, as currently the OVA through vCenter as well as through ESXi deploys with a single disk. Ellis and Bono do seem to come up successfully despite the error I am seeing, which makes me think it’s purely cosmetic but with knowing the correct disk controller type for vSphere which is intended by you I can make further modifications to the OVF to avoid the cosmetic error as well: [cw-aio]ubuntu@cw-aio:~$ netstat -ano | grep 5060 tcp0 0 10.27.32.111:5060 0.0.0.0:* LISTEN off (0.00/0/0) udp0 0 10.27.32.111:5060 0.0.0.0:* off (0.00/0/0) Kind Regards, Frank Escaros-Buechsel Consulting Architect NFV fescarosbue...@vmware.com<mailto:fescarosbue...@vmware.com> Parnell House, Barrack Square, Ballincollig, Co. Cork, P31 PF68, IRL Twitter: @fbuechsel Advanced notice of absence: [VMwareLogo] From: Frank Escaros-Buechsel Sent: Friday 20 April 2018 22:03 To: Roger Case Cc: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Roger, Looks like a malformed ofv file for the vsphere build you are using, I can try to reproduce in my lab over the weekend. Frank Escaros-Buechsel Consulting Architect NFV Parnell House, Barrack Square, Ballincollig, Co. Cork P31 PF68, IRL Twitter: @fbuechsel On 20 Apr 2018, at 22:58, Roger Case mailto:c...@gci.com>> wrote: Hi Frank, 1. Where would I get the checksum to compare with the one I derived from the downloaded file? 2. Unzip OK. 3. Checksums of .ovf and .vmdk match those in the .mf file 4. Same error when selecting all three unzipped files to deploy ovf. 5. Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:24 GMT+3, Roger Case mailto:c...@gci.com>> wrote: Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearw
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Roger, Looks like a malformed ofv file for the vsphere build you are using, I can try to reproduce in my lab over the weekend. Frank Escaros-Buechsel Consulting Architect NFV Parnell House, Barrack Square, Ballincollig, Co. Cork P31 PF68, IRL Twitter: @fbuechsel On 20 Apr 2018, at 22:58, Roger Case mailto:c...@gci.com>> wrote: Hi Frank, 1) Where would I get the checksum to compare with the one I derived from the downloaded file? 2) Unzip OK. 3) Checksums of .ovf and .vmdk match those in the .mf file 4) Same error when selecting all three unzipped files to deploy ovf. 5) Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:24 GMT+3, Roger Case mailto:c...@gci.com>> wrote: Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__projectclearwater.org&d=DwMF-g&c=uilaK90D4TOVoH58JNXRgQ&r=-TWQ2venLlorDb_G_vIJLhFd9harQeN_bur4qh28ZZY&m=nZ74kNJCYThrHTDSA3J_sWXkn3mizY8ISYbSJBKg24Y&s=2qwlj9Q3_bQcSmxUEMuhYsYgR9cLAYq8Yow_4Awb6sg&e=>) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes whic
Re: [Project Clearwater] Release note for Sprint Zamîn
1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:24 GMT+3, Roger Case wrote: Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__projectclearwater.org&d=DwMF-g&c=uilaK90D4TOVoH58JNXRgQ&r=-TWQ2venLlorDb_G_vIJLhFd9harQeN_bur4qh28ZZY&m=nZ74kNJCYThrHTDSA3J_sWXkn3mizY8ISYbSJBKg24Y&s=2qwlj9Q3_bQcSmxUEMuhYsYgR9cLAYq8Yow_4Awb6sg&e=>) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.projectclearwater.org_en_stable_Upgrading-5Fa-5FClearwater-5Fdeployment.html&d=DwMF-g&c=uilaK90D4TOVoH58JNXRgQ&r=-TWQ2venLlorDb_G_vIJLhFd9harQeN_bur4qh28ZZY&m=nZ74kNJCYThrHTDSA3J_sWXkn3mizY8ISYbSJBKg24Y&s=qcTPSTk5rbrrb9tKuc7vPepjpenEiPPEJ2lTtsmp9Es&e=>. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova<https://urldefense.proofpoint.com/v2/url?u=http-3A__vm-2Dimages.cw-2Dngv.com_cw-2Daio.ova&d=DwMF-g&c=uilaK90D4TOVoH58JNXRgQ&r=-TWQ2venLlorDb_G_vIJLhFd9harQeN_bur4qh28ZZY&m=nZ74kNJCYThrHTDSA3J_sWXkn3mizY8ISYbSJBKg24Y&s=PUMku_aSKgNoiXkqZ8ant31BoZ-iIM3wJCW24TKelsU&e=>) has been updated for this release. Cheers, Richard ___ Clearwater mailing list
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Frank, 1) Where would I get the checksum to compare with the one I derived from the downloaded file? 2) Unzip OK. 3) Checksums of .ovf and .vmdk match those in the .mf file 4) Same error when selecting all three unzipped files to deploy ovf. 5) Removing the .mf file and attempting to deploy the template using just the .ovf and .vmdk results in different errors: [cid:image001.png@01D3D89E.C6EEAF80] Thanks, Roger From: Frank Escaros-Buechsel [mailto:fescarosbue...@vmware.com] Sent: Friday, April 20, 2018 9:12 AM To: clearwater@lists.projectclearwater.org; Roger Case Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] 1)Verify the checksum to ensure you don’t have a corrupt download 2)unzip the ova into a folder, you will get an ovf, vmdk and mf file 3)run sha1 sum on all files separately, compare output against the values in mf file, if one deviates update the value in mf to correct one 4)do not zip again, deploy through web client and select ovf and all vmdk files This should let you deploy. Another way would be to follow step 1 and 2 and simply delete the mf file, as this will skip the checksum check (not recommended for environments which need to proof authenticity of uploaded files though) Hope that helps. Frank Sent from VMware Boxer On 20 April 2018 at 19:27:24 GMT+3, Roger Case mailto:c...@gci.com>> wrote: Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__projectclearwater.org&d=DwMF-g&c=uilaK90D4TOVoH58JNXRgQ&r=-TWQ2venLlorDb_G_vIJLhFd9harQeN_bur4qh28ZZY&m=nZ74kNJCYThrHTDSA3J_sWXkn3mizY8ISYbSJBKg24Y&s=2qwlj9Q3_bQcSmxUEMuhYsYgR9cLAYq8Yow_4Awb6sg&e=>) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.projectclearwater.org_en_stable_Upgrading-5Fa-5FClearwater-5Fdeployment.html&d=DwMF-g
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Will, No, also 6.0. Previous AIO, however. Other Metaswitch .OVA still work Sent from my GCiPhone On Apr 20, 2018, at 01:49, William Yates mailto:william.ya...@metaswitch.com>> wrote: [External Email] Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org<http://projectclearwater.org>) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Cheers, Richard ___ Clearwater mailing list Clearwater@lists.projectclearwater.org<mailto:Clearwater@lists.projectclearwater.org> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Roger, When this worked before, was it on a previous version of vSphere? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 19 April 2018 20:15 To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Cheers, Richard ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Will, vSphere 6.0, vCenter Server 6.5. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of William Yates Sent: Thursday, April 19, 2018 2:58 AM To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Cheers, Richard ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Re: [Project Clearwater] Release note for Sprint Zamîn
Hi Roger, Please could you tell me what version of vSphere you are using? Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Roger Case Sent: 18 April 2018 21:59 To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Release note for Sprint Zamîn Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Cheers, Richard ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Re: [Project Clearwater] Release note for Sprint Zamîn
Attempt to deploy vSphere OVF Template using downloaded cw-aio.ova from link below results in “The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1.” Am I missing something here? This worked before. Thanks! Roger From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Richard Whitehouse (projectclearwater.org) Sent: Tuesday, April 10, 2018 7:32 AM To: clearwater@lists.projectclearwater.org Subject: [Project Clearwater] Release note for Sprint Zamîn [External Email] Hi all, The release for Project Clearwater sprint “Zamîn” has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we’ve put a huge amount of effort into increasing Project Clearwater’s quality, as we know that reliability is extremely important to most users of IMS. We’re proud of where we’ve got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first “stable” release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It’s time to move our core development to a new phase, focussed more on stability, and less on new features. That’s going to mean that we won’t expect to tag new releases as frequently. It’s also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater’s reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Cheers, Richard ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
[Project Clearwater] Release note for Sprint Zamîn
Hi all, The release for Project Clearwater sprint "Zamîn" has been cut. The code for this release is tagged as release-130 in GitHub. This is a big release for us! Over the last year, we've put a huge amount of effort into increasing Project Clearwater's quality, as we know that reliability is extremely important to most users of IMS. We're proud of where we've got to, and we now recommend using this release whenever possible. To mark that, we are declaring Zamîn our first "stable" release. We think that Project Clearwater is now a well featured IMS core, built on a great architecture. It's time to move our core development to a new phase, focussed more on stability, and less on new features. That's going to mean that we won't expect to tag new releases as frequently. It's also going to free us up to spend more time blogging about Project Clearwater and IMS: watch this space. This release includes a number of bug fixes which improves Clearwater's reliability at performance and load. To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Cheers, Richard ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
