|
Doc Tools (Conversion from DevWiki to RTD / Debugging of RST Files)
#documentation
#doc
#onap-developer
I’d just like to share some information about two scripts provided by the doc team. The scripts where created mainly to ease the work of the doc team, but maybe they can help you in the process of dev
I’d just like to share some information about two scripts provided by the doc team. The scripts where created mainly to ease the work of the doc team, but maybe they can help you in the process of dev
|
By
Thomas Kulik
· #20512
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
Krzysztof, unfortunately it appears there were no release tags used in the past that can be pushed for these repos. Thanks, Mandar AT&T Proprietary (Internal Use Only) Not for use or disclosure outsid
Krzysztof, unfortunately it appears there were no release tags used in the past that can be pushed for these repos. Thanks, Mandar AT&T Proprietary (Internal Use Only) Not for use or disclosure outsid
|
By
Mandar Sawant
· #18845
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
Ping? Best regards,
By
Krzysztof Opasiak
· #18767
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
I confirm that repos are again available. Thank you very much for that! Would it be possible for you to push also release tags to the mentioned repositories? Most of them don't have any of them which
I confirm that repos are again available. Thank you very much for that! Would it be possible for you to push also release tags to the mentioned repositories? Most of them don't have any of them which
|
By
Krzysztof Opasiak
· #18471
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
Please check now. The repositories have been restored. AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement
Please check now. The repositories have been restored. AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement
|
By
Mandar Sawant
· #18468
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
Hello, These seem to have been accidentally deleted. I'm trying to find more information. I will keep you posted. Thanks, Mandar AT&T Proprietary (Internal Use Only) Not for use or disclosure outside
Hello, These seem to have been accidentally deleted. I'm trying to find more information. I will keep you posted. Thanks, Mandar AT&T Proprietary (Internal Use Only) Not for use or disclosure outside
|
By
Mandar Sawant
· #18449
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
Dear Mandar Sawant, could you please provide your feedback on below issues? Best regards, Krzysztof Opasiak
Dear Mandar Sawant, could you please provide your feedback on below issues? Best regards, Krzysztof Opasiak
|
By
Krzysztof Opasiak
· #18442
·
|
|
State of DMaaP AT&T legacy dependencies
#dmaap
#documentation
Hi Recently I was assigned a task of analyzing DMaaP and its external dependencies among other things. It was found that DMaaP (and as I understand it, some other ONAP subsystems as well) depend on a
Hi Recently I was assigned a task of analyzing DMaaP and its external dependencies among other things. It was found that DMaaP (and as I understand it, some other ONAP subsystems as well) depend on a
|
By
Jussi Iho
· #18393
·
|
|
#integration #documentation vFirewall Use Case documentation
#integration
#documentation
Hi, we just published our notes from vFWCL on Casablanca offline platform https://gerrit.onap.org/r/gitweb?p=oom/offline-installer.git;a=blob;f=docs/vFWCL-notes.rst;h=690b6dc9ec3c19cc225f6f495c8711b09
Hi, we just published our notes from vFWCL on Casablanca offline platform https://gerrit.onap.org/r/gitweb?p=oom/offline-installer.git;a=blob;f=docs/vFWCL-notes.rst;h=690b6dc9ec3c19cc225f6f495c8711b09
|
By
Michal Ptacek
· #17024
·
|
|
#integration #documentation vFirewall Use Case documentation
#integration
#documentation
Hi, ah so “DemoVFWCL” does not actually refer to VFWCL demo use case as such but to Demo customer? Therefore the automated test is also not really building up to run the whole demo arch (even though i
Hi, ah so “DemoVFWCL” does not actually refer to VFWCL demo use case as such but to Demo customer? Therefore the automated test is also not really building up to run the whole demo arch (even though i
|
By
Lasse Kaihlavirta
· #16975
·
|
|
#integration #documentation vFirewall Use Case documentation
#integration
#documentation
DemVFWCL uses the Demo customer so its not a full regression like instantiateVFWCL which creates a new customer and onboards a new model for each onboarding. The original intent was for instantiateVFW
DemVFWCL uses the Demo customer so its not a full regression like instantiateVFWCL which creates a new customer and onboards a new model for each onboarding. The original intent was for instantiateVFW
|
By
Brian Freeman
· #16974
·
|
|
#integration #documentation vFirewall Use Case documentation
#integration
#documentation
Hi, as was mentioned in Integration weekly meeting today, the latest (yet unpublished?) document version of vFWCL demo steps in integration master (dublin doesn't seem to be branched yet) is missing t
Hi, as was mentioned in Integration weekly meeting today, the latest (yet unpublished?) document version of vFWCL demo steps in integration master (dublin doesn't seem to be branched yet) is missing t
|
By
Lasse Kaihlavirta
· #16973
·
|
|
RKE HA collaboration for Kubernetes/Helm/Docker alignment
#oom
#integration
#documentation
Hi Michael, I have updated the integration scripts to use the following versions (also updated OOM-1598 with this info): · ubuntu 18.04 · docker 18.09.5 · rke 0.2.1 · rke kubernetes_version: v1.13.5-r
Hi Michael, I have updated the integration scripts to use the following versions (also updated OOM-1598 with this info): · ubuntu 18.04 · docker 18.09.5 · rke 0.2.1 · rke kubernetes_version: v1.13.5-r
|
By
Gary Wu
· #16700
·
|
|
RKE HA collaboration for Kubernetes/Helm/Docker alignment
#oom
#integration
#documentation
Gary, Hi, we (OOM) would like to continue our collaboration with yourself, Brian, Yang, Alain, Mike, Sylvain, Morgan, Eric, …and others inside devops teams on getting an HA deployment of RKE aligned v
Gary, Hi, we (OOM) would like to continue our collaboration with yourself, Brian, Yang, Alain, Mike, Sylvain, Morgan, Eric, …and others inside devops teams on getting an HA deployment of RKE aligned v
|
By
...
· #16661
·
|