Brian,

DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in 
the process of supporting other cloud for now.
This could be an enhancement for Beijing, if DCAE still runs in VMs. And if we 
do such implementation, we should leverage Multicloud interfaces to do so.

Prior to this, we should flush out the requirement of DCAE deployment on 
different type of cloud, what are the implications and so on.

Alexis

> On Jan 22, 2018, at 9:34 AM, FREEMAN, BRIAN D <[email protected]> wrote:
> 
> Michale, Alexis,
> 
> What is the current status of bring DCAE up on non-openstack clouds via OOM ? 
> I have gotten all components but DCAE to pass healthcheck but not sure 
> dcaegen2 pod is even starting in my Azure test environment.
> 
> Brian
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Michael O'Brien via 
> RT
> Sent: Friday, January 05, 2018 2:46 PM
> Cc: [email protected]; [email protected]
> Subject: Re: [onap-discuss] [ONAP Helpdesk #50702] Unable to create new JIRA 
> on mandatory "Affects Version" introduced today
> 
> Jessica,
>   Fixed - thank you
>   Verified task and bug creation
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_INT-2D376&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=tKrU0djaLFNMunPe64UL71aFWuRZOtZNphgsL0_tZww&e=
>   
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_INT-2D377&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=lmgLUdA1wy4X-hgZh5sG7g92G3dUW8ZBiQIzON1dVIg&e=
>  
> 
>   /michael
> 
> -----Original Message-----
> From: Jessica Wagantall via RT [mailto:[email protected]] 
> Sent: Friday, January 5, 2018 13:38
> To: Michael O'Brien <[email protected]>
> Cc: [email protected]; [email protected]
> Subject: [ONAP Helpdesk #50702] Unable to create new JIRA on mandatory 
> "Affects Version" introduced today
> 
> Dear Michael , 
> 
> Can you please try again. This mandatory field has now been isolated to only 
> Bug type issues on its own. Epic and Story can now be created without the 
> need of an Affected Version. 
> 
> Please try and let me know. 
> 
> Thanks and sorry for the trouble
> Jess
> 
> On Fri Jan 05 13:33:22 2018, jwagantall wrote:
>> Working on this now.. 
>> 
>> thanks!
>> Jess
>> 
>> On Fri Jan 05 08:17:31 2018, [email protected] wrote:
>>> Jessica,
>>>   Hi, JIRA currently is broken on the new validation field - we are 
>>> not able to add any new issues - could we get this addressed ASAP, 
>>> either temporarily reverse the change and retest it before 
>>> reintroducing it or temporarily auto-populating it
>>> 
>>> Thank you
>>> /michael
>>> 
>>> -----Original Message-----
>>> From: ONAP Helpdesk via RT [mailto:onap- 
>>> [email protected]]
>>> Sent: Friday, January 5, 2018 00:44
>>> To: Michael O'Brien <[email protected]>
>>> Subject: [ONAP Helpdesk #50702] AutoReply: Unable to create new JIRA 
>>> on mandatory "Affects Version" introduced today
>>> 
>>> Greetings,
>>> 
>>> Your support ticket regarding:
>>>        "Unable to create new JIRA on mandatory "Affects Version"
>>> introduced today", has been entered in our ticket tracker.  A 
>>> summary of your ticket appears below.
>>> 
>>> If you have any follow-up related to this issue, please reply to 
>>> this email.
>>> 
>>> You may also follow up on your open tickets by visiting 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__rt.linuxfoundation.org_&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=FXckY0PVLNJI-0IyLaAM6k6lmgsRtC5iXouWEJ8SEcU&e=
>>>   -- if you have not logged into RT 
>>> before, you will need to follow the "Forgot your password" link to 
>>> set an RT password.
>>> 
>>> --
>>> The Linux Foundation Support Team
>>> 
>>> 
>>> --------------------------------------------------------------------
>>> -----
>>> LF,
>>>  Hi, I totally agree with the new mandatory field "affects version"
>>> - however I have tried adjusting the "configure fields" section and 
>>> an unable to raise any Epic or Story anymore because of the blocking 
>>> error on this field - which does not show on the create issue screen.
>>>   Setting the "Fix Version/s" field does not help.
>>>   Can you adjust the "Create Issue" screen so we can fill in this 
>>> mandatory field
>>> 
>>> 
>>> [cid:[email protected]]
>>>    thank you
>>>   /Michael
>>> 
>>> This message and the information contained herein is proprietary and 
>>> confidential and subject to the Amdocs policy statement,
>>> 
>>> you may review at 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=cwcQx-lb5lvCNmnJ6UvcPywCAUokSHPPUtuuEMBOiM8&e=
>>>  
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=cwcQx-lb5lvCNmnJ6UvcPywCAUokSHPPUtuuEMBOiM8&e=
>>>  >
>>> 
>>> This message and the information contained herein is proprietary and 
>>> confidential and subject to the Amdocs policy statement,
>>> 
>>> you may review at 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=cwcQx-lb5lvCNmnJ6UvcPywCAUokSHPPUtuuEMBOiM8&e=
>>>  
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=cwcQx-lb5lvCNmnJ6UvcPywCAUokSHPPUtuuEMBOiM8&e=
>>>  >
>> 
>> 
> 
> 
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=cwcQx-lb5lvCNmnJ6UvcPywCAUokSHPPUtuuEMBOiM8&e=
>   
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=cwcQx-lb5lvCNmnJ6UvcPywCAUokSHPPUtuuEMBOiM8&e=
>  >
> 
> _______________________________________________
> onap-discuss mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=RxRLDQIecOhG_dzWswNA19mVloRixnSnvKdyBDYaeLI&e=
>  
> _______________________________________________
> onap-discuss mailing list
> [email protected]
> https://lists.onap.org/mailman/listinfo/onap-discuss

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to