public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Venkata Pyla" <venkata.pyla@toshiba-tsip.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [PATCH 3/3] README: Add steps to build cip-security image
Date: Thu, 23 Jul 2020 23:58:28 -0700	[thread overview]
Message-ID: <30764.1595573908018751968@lists.cip-project.org> (raw)
In-Reply-To: <544b0f34-c55b-2be1-d672-6a5eb796403e@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

Hi Jan,

On Thu, Jul 23, 2020 at 04:10 PM, Jan Kiszka wrote:

>
> On 21.07.20 10:16, Venkata Pyla wrote:
> > From: venkata <venkata.pyla@toshiba-tsip.com>
> > 
> > Signed-off-by: venkata <venkata.pyla@toshiba-tsip.com>
> > ---
> >   README.md | 10 ++++++++++
> >   1 file changed, 10 insertions(+)
> > 
> > diff --git a/README.md b/README.md
> > index bbad1a0..b2c4166 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -36,6 +36,16 @@ card, run
> >       dd
> if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-buster-bbb.wic.img \
> >          of=/dev/<medium-device> bs=1M status=progress
> >   
> > +## Building Security target images
> > +Building images for QEMU x86-64bit machine
> > +
> > +    ./kas-docker --isar build --target cip-core-image-security
> kas.yml:board-qemu-amd64.yml
> > +
> > +Run the generated securiy images on QEMU (x86-64bit)
> > +
> > +    TARGET_IMAGE=cip-core-image-security ./start-qemu.sh amd64
> > +
> > +
> >   ## Community Resources
> >   
> >   TBD
> > 
> 
> This patch is fine, but I'm missing 4/4: Add this image to CI (same 
> comment as I had on the MR on gitlab).
> 

Adding cip security image to CI, 
i need some suggestions to use the current format present in .gitlab-ci.yml

Currently i have the below problem for using script deploy-cip-core.sh:
1. image name formation in the script should have another variable
         .../$IMG_PREFIX-cip-core-$RELEASE-$TARGET
         where $IMG_PREFIX is default to "cip-core-image"  if not specified
          for security image it will be passed as 4th argument "cip-core-image-security"
2. currently scrit is expecting the image format in *.wic.img so,
       for qemu i think we should have wks file to generate image with format .wic.img

or for this security image do we need to deploy it seperatley?
please guide me

Thanks

> Jan
> 
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4992): https://lists.cip-project.org/g/cip-dev/message/4992
Mute This Topic: https://lists.cip-project.org/mt/75699595/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-07-24  6:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  8:16 [cip-dev] [PATCH 1/3] cip-security: Add packages for IEC-62443-4-2 Evaluation Venkata Pyla
2020-07-21  8:16 ` [cip-dev] [PATCH 2/3] start-qemu.sh: use TARGET_IMAGE to pick respective image file Venkata Pyla
2020-07-21  8:16 ` [cip-dev] [PATCH 3/3] README: Add steps to build cip-security image Venkata Pyla
2020-07-23 10:40   ` Jan Kiszka
2020-07-24  6:58     ` Venkata Pyla [this message]
2020-07-30  0:07       ` Daniel Sangorrin
2020-07-30  5:59         ` Jan Kiszka
2020-07-23 10:37 ` [cip-dev] [PATCH 1/3] cip-security: Add packages for IEC-62443-4-2 Evaluation Jan Kiszka
2020-07-23 12:53   ` Venkata Pyla
2020-07-23 13:13   ` Venkata Pyla
2020-07-23 13:52     ` Jan Kiszka
2020-07-27  2:47       ` Daniel Sangorrin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30764.1595573908018751968@lists.cip-project.org \
    --to=venkata.pyla@toshiba-tsip.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox