I am creating my Sagemaker notebook instance using terraform. I want to add my git repository with Sagemaker notebook instance at the time of instance creation.
Please help me if there is any solution for the same.
Thank you for using Amazon SageMaker!
SageMaker supports associating git repositories to Notebook Instance which gets added to Notebook Instance during Create/Start.
Please checkout our blog post of how to add git repository to your Notebook Instances git repository integration.
For more information please see our documentation here.
Thanks,
Neelam
To extend this thread
Instead of adding a repo at notebook instance creation time, I need to add an additional repo (a CodeCommit repo) to an existing instance. In order to do that, I used the following steps:
add the CodeCommit repo to the Sagemaker account
stop the notebook instance if it is running
Edit the instance to add the repo as an additional git repo
wait for the notebook instance to finish updating
start the instance
Then the new repo will show up next to the existing repos in the instance's UI
Related
I am using Google Cloud to deploy my application. I have followed the steps in the documentation for deploying. I deployed early on in my project and it was successful. I then decided to change some files and update some features in my app. For this i followed the documentation for updating a deployment. This update was successful. It had me create the deployment in my Deployment Manager and run the gcloud commands to commence update. When I redeployed with gcloud app deploy, it was successful.
I have since added a couple more lines of code and features in my application. I followed the same documentation for updating a deployment as I had the first time I made an update and it is no longer working for me.
Does anybody have any idea what would be the problem? Again, I was able to successfully deploy, and even update that deployment once by following Google Cloud docs. Now I am having no luck.
Have you been changing the version number? Go to:
https://console.cloud.google.com/appengine/versions?project=< your project name >&serviceId=default
And make sure the version you want is active. Also, you can try:
http://<VERSION>-dot-<SERVICE>-dot-<PROJECT_ID>.<REGION_ID>.r.appspot.com
Example:
https://20200813-dot-myapp.uc.r.appspot.com
if the version number was 20200813 and your appname is myapp and the region is uc
I have a DC/OS cluster running a local instance of 'universe'. What is the specific procedure for adding custom packages to a local 'universe'? The only documentation I have found so far (which is very limited), is related to adding packages to the global universe repo. While this is great for the DC/OS community, it does not help in regards to maintaining private universes and repos.
The only procedures I found say:
1-Create a fork of the public universe repo: https://github.com/mesosphere/universe
2-Creating a custom package and then resubmitting it back to the community.
This is not exactly what I was expecting to see. I was hoping for a simple local package creation process. Is there such a thing?
Thanks,
GAOTU
Fork this universe repo and clone the fork:
git clone https://github.com/<user>/universe.git /path/to/universe
Add your package to the repo in right folder. Write the necessary markup files
(config.json, marathon.json.mustache, resource.json, package.json etc.)
Run the verification and build script to validate and build the Universe artifacts:
scripts/build.sh
This verifies the syntax of the files you added.
Build the Universe Server Docker image:
DOCKER_TAG="my-package" docker/server/build.bash
This will create your docker image of local universe(ngnix server) and marathon.json to start the universe server.
Run Universe Server
dcos marathon app add marathon.json
Point DC/OS to local universe server
dcos package repo add --index=0 dev-universe http://universe.marathon.mesos:8085/repo
Install your newly added package in DC/OS cluster
dcos package install new_package
Do you want to add the package to your local universe, correct (i.e., not the mesosphere universe)?
In this case, after creating your custom package (and yes, there should be better documentation...) you can add this local/custom universe to a DC/OS cluster: https://dcos.io/docs/1.7/usage/repo/#adding
In general, you don't even have to fork the universe: a package repo is basically a simple folder structure. Check out the universe_builder.py here : It build a zip file, uploads it to S3, which you can then add as a new package repository as described above (and as output by the script).
In general feel to contribute and help to help improve the documentation!
I am been using Acquia trial account. I have setup the project repository on the same. Now I want to clone the staging environment on my local machine but I am able to do that whereas I am able to clone dev environment successfully as per the mention steps.
Can anyone please help with the steps for cloning the Acquia Stage Environment.
I'm trying google cloud for my PHP site. I use bitbucket git repo and connected it to my google cloud account. Now I want to test the push-to-deploy feature. I set the release pipeline so that any git push to the bitbucket repo supposed to be deployed automatically to the compute engine. But it just won't get deployed at all. Google doesn't show anything on the commit table in the release pipeline page, although we could see that the code is successfully updated via Browse menu.
The Google little changed the feature of push to deploy. Now you have to create the Jenkins Instance to build and test your application. Go through the docs [1] and follow the steps.
[1] Pushto deploy: https://cloud.google.com/tools/repo/push-to-deploy
I've recently started with Appengine and I'd been using the regular old deployment method using appcfg.py.
Now I want to start deployment using release pipelines. I created a pipeline in my Project settings, then authenticated myself in gcloud.
Now if I do gcloud init myproj-id, I should theoretically get the content of my project pulled from the server right? But that doesn't happen.
https://developers.google.com/cloud/sdk/gcloud/reference/init
If you have enabled push-to-deploy in the Cloud Console, one of the
things that gcloud init will do for you is cloning the Google-hosted
git repository associated with PROJECT
So, my questions:
Why is the content not pulled?
What happens if I push my project via git now? How would Appengine manage my previously deployed project via appcfg.py versus my git push'd project?
Why is the content not pulled?
Did you configure your repository by using the Configure your repository link at the top of the pipeline configuration page?
What happens if I push my project via git now? How would Appengine manage my previously deployed project via appcfg.py versus my git push'd project?
Unless you use different versions, App Engine won't make a difference; your git pushed project will overwrite your previous one.