Trolling ! No. Finnish - One can find translation in youtube comment section.
The debate is important for third world where education , job market and govt get polarized and which is almost a complete Bill Gates' territory now. To put in simple terms, after LF course/training.........what next !
Can freedom or FOSS sustain when a single person owns github , mandates linkedIn , compromises CEOs and govts, dictates outsourcing ( all this while chanting globalization ) without legacy of Linus giving it a tough opposition.
Its should be openly debated , nothing personal here.
Even if you mark the course as completed, you still have access to the course content for what is left of your 1 year access (until 11/28/2019). To access the course once you mark the course completed, you will go to your portal, and launch it under the Previous Classes tab. I hope this helps. Please let us know if you have additional questions.
From your second output above, you have coredns pods running, the default DNS server now. Kube-dns is no longer used, although you may see a kube-dns service in your cluster, which merely exposes the coredns pods (the name was kept for compatibility).
More on DNS here.
The first output seems to resolve the nginx service to the 10.98.x.x IP. And that should be the correct IP, so I do not see anything wrong there. Based on your DNS configuration, it also tries to resolve the nginx service against other entries in your resolver configuration file - and as expected, they all fail.
*Revised comment for explanation to everyone
Hey everyone just to be clear., if you receive the error:
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: API error (404): network startFiles_basic not found
Head into your docker-compose file and replace the line:
wtih this line.
Explanation: The old method used to work, but as of 1.4 the error occurs much more often. We will be removing this with the next update
Alternatively You do have the option to override the value inside of the container, which may work as well.
@PaulAmehUgw1 It looks like your pathing for CORE_PEER_MSPCONFIGPATH is broken toward the end. Please double check it for breaks. The value should be one solid command.
Please fix that and then rerun the command
I had the same problem and I will describe what helped me, maybe is the same solution.
When you do lab 1, you execute the script startup.sh. Inside this script there is a instruction to download another script called bootstrap.sh.
Besides other things, startup.sh executes bootstrap.sh and later on deletes it. What bootstrap.sh does follows:
If for example, generating or creating the channel fails, you will not know right away. In addition to that bootstrap.sh is deleted, so you get confused if you don't check if every instruction was successful.
What I did was:
Try this and let me know.
From my knowledge, it's just that we need to hit different apis to get different features/details. Just a random example if we want to get details of a node we need to hit api a, whereas if we want to get details of pods, we need to hit api b.
Did you try to change the "Select Boot Source" to Instance Snapshoot? In my case just then the newly created "image" appears.
@selewicz: Is there a way to convert an image from the "instance snapshoot" into a simple "image" without downloading and then uploading it back to the OpenStack?
it seems that the knowledge check mentioned in the titel is wrong. I select the keystone as the answer but the check says incorrect.
I have heard back from the infrastructure person. It seems that the pt-get update issues were due to a mirror what had issues for a bit, but is back in working order.
As for the devstack install issues, this seems to be tied to ongoing work in the Pike release github source, where configuration files were changed and an "undocumented feature" was introduced. Should the code not be updated back to expected manner in a timely manner I will update the content for whichever the new installation process of the Pike it may call for. This was not an expected change by the community, as sometimes happens with open source and fast changing projects.
Thank you again for contacting us,