[
https://issues.apache.org/jira/browse/BIGTOP-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328215#comment-14328215
]
Olaf Flebbe commented on BIGTOP-1627:
-------------------------------------
Thank you very much for looking into this!!!
Tested on debian. Did not work since apt usually forces repositories have to be
signed. I signed my bigtop repo and the gpg signature check fails, because of
the missing key. See below for error message.
So either we have to support signed repositories or we have to force apt not to
check signatures.
IMHO it wold be best to use the 'apt' puppet class to set up the apt location
and supply a 'disable_keys' equals true parameter.
Too late tonight to give a concrete patch now...
Instructions to create a signed repo:
The repo can be signed with this patch:
{code}
diff --git a/bigtop-repos/apt/distributions b/bigtop-repos/apt/distributions
index 470bb7e..b9c547a 100644
--- a/bigtop-repos/apt/distributions
+++ b/bigtop-repos/apt/distributions
@@ -6,3 +6,4 @@ Version: 0.1
Architectures: i386 amd64 source
Components: contrib
Description: Bigtop
+SignWith: default
{code}
There must be a gpg key "default" in your keychain for this to work.
The
Somehow the vm needs access to the exported public gpg key (for instance named
keys.asc) and issue the command
"apt-key add key.asc" For instance we could use the convention to distribute
the key in the repository itself at its root level.
{code}
...
Debug: Executing '/usr/bin/dpkg-query -W --showformat '${Status} ${Package}
${Version}\n' hadoop-hdfs-datanode'
Debug: Executing '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold
install hadoop-hdfs-datanode'
Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install hadoop-hdfs-datanode' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
bigtop-jsvc bigtop-utils hadoop hadoop-hdfs libjline-java liblog4j1.2-java
libnetty-java libservlet2.5-java libslf4j-java libxerces2-java
libxml-commons-external-java libxml-commons-resolver1.1-java
libzookeeper-java libzookeeper-java-doc netcat-openbsd zookeeper
Suggested packages:
libjline-java-doc libmail-java liblog4j1.2-java-doc libcommons-logging-java
libxerces2-java-doc libxerces2-java-gcj libxml-commons-resolver1.1-java-doc
The following NEW packages will be installed:
bigtop-jsvc bigtop-utils hadoop hadoop-hdfs hadoop-hdfs-datanode
libjline-java liblog4j1.2-java libnetty-java libservlet2.5-java
libslf4j-java libxerces2-java libxml-commons-external-java
libxml-commons-resolver1.1-java libzookeeper-java libzookeeper-java-doc
netcat-openbsd zookeeper
0 upgraded, 17 newly installed, 0 to remove and 14 not upgraded.
Need to get 4975 kB/40.9 MB of archives.
After this operation, 59.5 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
bigtop-utils bigtop-jsvc hadoop hadoop-hdfs hadoop-hdfs-datanode
E: There are problems and -y was used without --force-yes
{code}
> Move enable_local_yum implementation to bigtop-deploy/utils/setup-env.sh to
> share with Docker provisioner
> ---------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1627
> URL: https://issues.apache.org/jira/browse/BIGTOP-1627
> Project: Bigtop
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Assignee: Evans Ye
> Priority: Minor
> Labels: deployment, vm
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1627.1.patch, BIGTOP-1627.2.patch,
> BIGTOP-1627.3.patch
>
>
> Currently, we have *enable_local_yum* feature implemented in
> *vagrant-puppet-vm*'s Vagrantfile(see BIGTOP-1562's patch). This jira is
> proposing to move the implementation to {{bigtop-deploy/utils/setup-env.sh}}
> so that the we can share the general implementation between BigTop's VM
> provisoner and Docker provisioner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
